Attribute detail
todo
11 ideas · 2 distinct values
| Value | Distribution | Ideas | Share |
|---|---|---|---|
| true |
|
10 | 90.9% |
| deep links into HTML export pages when an export exists |
|
1 | 9.1% |
| Idea | Value | Status | Tags | Summary |
|---|---|---|---|---|
| base_linking | true | A base may have one-directional relationships with other bases. This follows a subscription model. Bases may be cross subscribed. Unless linked, than bases remain isolated. Base linking is configured in the config file in the base. reqlan directory. - an unlinked child base should sever the contained ideas from the parent base ( i. e. the parent should just see the child as a separate base and child ideas shouldn't be visible, the indexer shouldn't crawl it. ) they should be functionally distinct - bases, distinct from eachother in the system file tree, should be linkeable ( either one way or both ways ) - A linked child base should allow the parent base to see the child's ideas. The indexs should be linked, and the child counts etc should be included in the parents. - A child base should always be able to link to parent base ideas. | ||
| base_modes | true | A base may be linked to | ||
| watch | true | The cli should be able to watch a base and maintain the index as files change. | ||
| decompose | true | A command pallete action for decomposition. Should replace an idea with a reference to a new file that holds the old contents. Should accept multiple inputs and put them in a list. e. g. to ( ideainputname, defaulting to concatenation ) | ||
| open_a_random_requirement | true | as it sounds | ||
| pallete_function_create_todo | true | A function that opens up a modal webview form allowing the user to write a rq-idea, search for references etc, and writes it to a specified output file. default folder is next to current file, but should be selectable in form. This behaviour should be configurable via ["./configuration.rq"] | ||
| index_comment_reference_inclusion | true | The [comment_grammar] comments should be included as a node type in the index | ||
| refernce_lists_pane_reference_tiering | true | Inbound refernces may be direct, or via ideaset references. The [reference_lists_pane] should tier the references based on the reference type. Design must keep in mind that that the ideaset refernces are likely more numerous and lower signal. | ||
| overview_page | deep links into HTML export pages when an export exists | First tab: a workspace overview for the active base — product-facing copy ( not index / debug jargon ). - At a glance: idea count, reference count, issues, bases, and a friendly readiness status. - Coverage: collapsible [overview_coverage_scores] ( lazy, non-blocking ). - Search: live cross-surface search over ideas, ideasets, attributes, and references for the active base; results group by surface with sample hits and actions to open the matching tab with the query applied ( [overview_search] ). - Export: buttons that open export functionality — Export form / HTML, and PDF ( [features_export.export_webview], [features_export] pdf path ). - Links: project site, support / email, GitHub. - Recent changes preview ( idea names when available ) with a link to [timeline_page]. | ||
| inbound_inlay_hints_whole_graph | true | done | Inbound references shown in [view_references_as_inlay_hints] should include referencers from the whole requirement graph across the workspace, not only ideas declared in the current file. Implemented by ["../../../packages/language/src/reqlan-inbound-reference-inlay-label.ts"], ["../../../packages/language/src/reqlan-inlay-hint-provider.ts"]. [view_references_as_inlay_hints] [traceable_inlay_hints] | |
| index_code_files | true | The indexer should be able to index non-rq files as well for comment references. |