lambda-erp 0.1.30__tar.gz → 0.1.31__tar.gz

{lambda_erp-0.1.30 → lambda_erp-0.1.31}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: lambda-erp
-Version: 0.1.30
+Version: 0.1.31
 Summary: Core ERP logic - accounting, sales, purchasing, inventory
 Author: TORUS INVESTMENTS AG
 License-Expression: MIT

{lambda_erp-0.1.30 → lambda_erp-0.1.31}/api/chat.py

@@ -1720,6 +1720,7 @@ Use the line `frequency` for a recurring item that is genuinely part of the quot
 The `remarks` (Notes / Terms) field on quotations, sales orders, and invoices renders on the PDF with a small markup vocabulary, so when a user dictates offer notes, conditions, recurring services, or a sign-off you can compose a polished closing block instead of a flat paragraph. Put this ONLY in `remarks` (never in item descriptions):
 - `# Heading` at the start of a line -> bold heading
 - `*italic*` or `_italic_` -> italic; `**bold**` -> bold
+- `---` (a line of 3+ dashes) -> a full-width thin horizontal rule (divider)
 - A line starting with `>>` is a price line, split by the FIRST `|` pipe: the text BEFORE the pipe goes in the left (frequency) column, the text AFTER it in the right (amount) column — both placed literally as you write them, NOT interpreted (it does not know "Monatlich" is a frequency or that "CHF 380" is a number). Omit the pipe to put everything in the amount column. The two columns line up with the line-items table's frequency/amount columns, so use it for a separately- or recurring-billed item, e.g. `>> Monatlich | CHF 380.—`.
 - Separate blocks with a blank line; a single newline is just a line break.
 Plain text (no special characters) still renders fine, so only reach for the markup when it improves a customer-facing note.

{lambda_erp-0.1.30 → lambda_erp-0.1.31}/api/remarks_md.py

@@ -16,6 +16,7 @@ Syntax (authored in the same textarea, also what the chat assistant emits):
   **bold**                -> bold
   >> Monatlich | CHF 380.—  -> right-aligned price box (period over amount),
                                floated beside the block's heading/description
+  --- (3+ dashes)         -> a full-width horizontal rule
 Everything is HTML-escaped first, so user text can't inject markup.
 """
 import html
@@ -64,6 +65,7 @@ def _block(lines):
 
     for raw in lines:
         stripped = raw.lstrip()
+        s = raw.strip()
         if stripped.startswith(">>"):
             flush_para()
             price_html += _price(raw)
@@ -71,6 +73,10 @@ def _block(lines):
             flush_para()
             heading = stripped.lstrip("#").strip()
             body += f'<div class="rm-h">{_inline(heading)}</div>'
+        elif len(s) >= 3 and set(s) == {"-"}:
+            # A line of 3+ dashes -> a full-width horizontal rule.
+            flush_para()
+            body += '<div class="rm-hr"></div>'
         else:
             para.append(raw)
     flush_para()

{lambda_erp-0.1.30 → lambda_erp-0.1.31}/api/templates/document.html

@@ -55,6 +55,7 @@
   .remarks .rm-h + .rm-p, .remarks .rm-p + .rm-p { margin-top: 2px; }
   .remarks .rm-amt { float: right; text-align: right; margin: 0 0 4px 16px; }
   .remarks .rm-amt-val { white-space: nowrap; }
+  .remarks .rm-hr { border-top: 1px solid #d1d5db; margin: 6px 0; }
   .remarks em { font-style: italic; }
   .remarks strong { font-weight: 700; }
 </style>

{lambda_erp-0.1.30 → lambda_erp-0.1.31}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "lambda-erp"
-version = "0.1.30"
+version = "0.1.31"
 description = "Core ERP logic - accounting, sales, purchasing, inventory"
 readme = "README.md"
 license = "MIT"