Attribute detail
plan
3 ideas · 3 distinct values
| Value | Distribution | Ideas | Share |
|---|---|---|---|
| goal Allow reqlan string literals in imports, idea names, and bracketed file/reference targets to use either double or single quotes with backslash escaping. constraints - [string_literals] documents escaping rules; double-quoted syntax must remain valid. - [reference_file] bracketed quoted paths must resolve with either quote style. - Embedded scanners and comment reference parsing must not treat // inside quoted strings as comments. steps 1. Extend grammar STRING terminal and shared unquote helper for both quote styles. 2. Update import/path/comment/embedded reference scanners and completion to accept single-quoted literals. 3. Update TextMate highlighting for single-quoted strings. 4. Add parsing and reference-resolution tests for single-quoted paths and idea names. open questions - None for initial scope; both quote styles apply everywhere STRING is used. |
|
1 | 33.3% |
| order ( agent_context_showcase interlock_showcase broken_links_showcase firmware_cloud_contract_showcase audit_trail_showcase module_surface_showcase test_proves_showcase legacy_archaeology_showcase graph_view_showcase attribute_dialect_showcase antipatterns_showcase ) |
|
1 | 33.3% |
| steps ( - do the thing - do the other thing ) |
|
1 | 33.3% |
| Idea | Value | Status | Tags | Summary |
|---|---|---|---|---|
| my idea2 | steps ( - do the thing - do the other thing ) | pending | todo, highpriority | it should be compatible with [[myidea]]. [[myidea|We can use obsidian-style-aliases]] which are also supported. |
| string_and_reference_apostrophes | goal Allow reqlan string literals in imports, idea names, and bracketed file/reference targets to use either double or single quotes with backslash escaping. constraints - [string_literals] documents escaping rules; double-quoted syntax must remain valid. - [reference_file] bracketed quoted paths must resolve with either quote style. - Embedded scanners and comment reference parsing must not treat // inside quoted strings as comments. steps 1. Extend grammar STRING terminal and shared unquote helper for both quote styles. 2. Update import/path/comment/embedded reference scanners and completion to accept single-quoted literals. 3. Update TextMate highlighting for single-quoted strings. 4. Add parsing and reference-resolution tests for single-quoted paths and idea names. open questions - None for initial scope; both quote styles apply everywhere STRING is used. | strings should use double or single apostrophes interchangeably and support backslash escapes. | ||
| phase_4_write_the_eleven | order ( agent_context_showcase interlock_showcase broken_links_showcase firmware_cloud_contract_showcase audit_trail_showcase module_surface_showcase test_proves_showcase legacy_archaeology_showcase graph_view_showcase attribute_dialect_showcase antipatterns_showcase ) | done | Write the eleven, one at a time, each validated by [phase_1_parse_gate] before moving on. Flagships first — [agent_context_showcase], [interlock_showcase], [broken_links_showcase], [firmware_cloud_contract_showcase] — so the format can be judged before committing to all eleven. |