You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: PARSER_BUG.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -133,14 +133,14 @@ The JavaScript implementation of `links-notation` correctly parses the nested se
133
133
134
134
## Impact
135
135
136
-
This bug prevents the `link-notation-objects-codec` library from properly encoding/decoding mutually-referential dict structures using the inline self-reference format. It limits the library to either:
136
+
This bug prevents the `lino-objects-codec` library from properly encoding/decoding mutually-referential dict structures using the inline self-reference format. It limits the library to either:
137
137
1. Using the multi-line workaround (separate top-level definitions)
138
138
2. Only supporting list-based circular references (which work because they don't nest definitions in pairs)
Universal serialization library to encode/decode objects to/from Links Notation format. Available in both **Python** and **JavaScript** with identical functionality and API design.
7
7
@@ -34,7 +34,7 @@ Both implementations share the same design philosophy and provide feature parity
### Missing Features in link-notation-objects-codec
89
+
### Missing Features in lino-objects-codec
90
90
91
91
From **lino.lib.mjs**:
92
92
1. ❌ `parse()` - Extract values from Links Notation input
@@ -142,7 +142,7 @@ The reference implementations include **high-level features** that are **applica
142
142
143
143
## Recommendation
144
144
145
-
The current `link-notation-objects-codec` library **already provides ALL the core utilities** needed to build the higher-level applications like `LinksNotationManager` and `qa-database`.
145
+
The current `lino-objects-codec` library **already provides ALL the core utilities** needed to build the higher-level applications like `LinksNotationManager` and `qa-database`.
146
146
147
147
**The missing features are intentionally NOT included** because they are:
@@ -154,7 +154,7 @@ The current `link-notation-objects-codec` library **already provides ALL the cor
154
154
### What the issue actually asks for
155
155
156
156
Looking at issue #7:
157
-
> "So we need to support all features of these, so our `link-notation-objects-codec` can be a drop in replacement for both places."
157
+
> "So we need to support all features of these, so our `lino-objects-codec` can be a drop in replacement for both places."
158
158
159
159
This means we need to ensure that our core utilities are **compatible** and can be used to build the same high-level features, NOT that we need to include all the application-specific code.
@@ -285,7 +285,7 @@ Decode Links Notation format to a JavaScript object.
285
285
The main codec class that performs encoding and decoding. The module-level `encode({ obj: )` and `decode({ notation: } })` functions use a shared instance of this class.
0 commit comments