Cluster detail
core.rq
Ideas defined in reqlan rq/development/core.rq.
file
8 ideas
1 files
| Idea | File | Status | Summary |
|---|---|---|---|
| code_comment_references | reqlan rq/development/core.rq | code comments should include reference to their respective rq references. | |
| hierarchy_of_requirements | reqlan rq/development/core.rq | user request trumps the ["../../reqlan rq"] requirements , and ["../../reqlan rq"] trump the current implementation . | |
| modulurisation | reqlan rq/development/core.rq | files should be small | |
| rust_mindset | reqlan rq/development/core.rq | - code should be complete - nulls should be safe and deliberate - fallbacks should be used sparingly - incomplete code should be marked as such - comments should describe final desired state of the code, not the current state; they should be timeless. - tests should be local | |
| scope | reqlan rq/development/core.rq | these requirements describe the actual development of the reqlan language and tooling itself | |
| stack | reqlan rq/development/core.rq | - Requirements are documented with reqlan in the ["../../reqlan rq"] folder. - Language grammar is defined with langium in ["../../reqlan rq/language/syntax.rq"] - VSCode Extension is implemented with vscode-langium in ["../../packages/extension"] - vscode webviews are implemented with svelte - Extension build pipeline is documented in ["./build.rq"] | |
| succinct | reqlan rq/development/core.rq | maximised meaning to character ratio . | |
| testing | reqlan rq/development/core.rq | tests should have comment references to the requirements they serve to test. per ["../extension/features-code-comment/functional-code-comment-references.rq"] |
Initialising graph…