spec - features-imports.rq

Idea	File	Status	Summary	Katz
anonymous_reference_code_completion	reqlan rq/extension/language/support/features-imports.rq		Anonymous imports should share the same code completion e. g. ["@/reqlan rq/extension/language/syntax/features-syntax.rq"] should complete the same as `import "@/reqlan rq/extension/language/syntax/features-syntax.rq" as code_completion`. they should share the same code and logic	0.053
from_import_syntax	reqlan rq/extension/language/support/features-imports.rq		Multiple symbols should be allowd to be be imported with `from "path" import symbol1, symbol2, symbol3` syntax. Each imported name is its own link ( ["../../../language/imports.rq".import_from] ).	0.040
implicit_file_extension	reqlan rq/extension/language/support/features-imports.rq		The import statements should not require an extension, i. e. it should assume ". rq " unless otherwise specified. An extensionless path resolves to the ". rq " file first, then to a literal extensionless file or folder. A path that already carries any extension is resolved exactly as written. Folder targets: [import_folder_targets].	0.195
import_code_completion	reqlan rq/extension/language/support/features-imports.rq		Import path code completion for `import` / `from` strings ( and shared anonymous paths ). [code_completion] [import_code_completion_explicit_extension] [import_code_completion_path_segments] [import_code_completion_substring_match] [import_code_completion_ranking] [anonymous_reference_code_completion] [import_code_completion_auto_file_import] [import_code_completion_rendering]	0.057
import_code_completion_auto_file_import	reqlan rq/extension/language/support/features-imports.rq	done	When a code completion for an idea in another file is selected, the import should be automatically added to the current file. This prevents the user from selecting a presented idea, and then having to add the import for the same thing. Uses the same from-import insertion as [import_error] quick fixes; skips the edit when the idea is already imported. [reference_code_completion] [import_code_completion] [import_code_completion_rendering] [import_error]	0.066
import_code_completion_explicit_extension	reqlan rq/extension/language/support/features-imports.rq		Completions insert paths with an explicit `.rq` extension. [implicit_file_extension] Hand-written imports may still omit the extension; completion prefers the written form with `.rq`.	0.047
import_code_completion_path_segments	reqlan rq/extension/language/support/features-imports.rq		In a folder context, show next path segments ( directories with a trailing `/` ). After `../`, offer `../path/` before nested `../path/file.rq`.	0.047
import_code_completion_ranking	reqlan rq/extension/language/support/features-imports.rq		Rank import path completions by directory proximity ( hop count from the completing file's directory to the candidate's directory ), then directories before files, then path alphabetically. Example: typing `../` ranks `../close.rq` before `../../../path.rq`. Emit sortText for that order, and set filterText so the editor does not re-rank by label fuzzy score over proximity.	0.053
import_code_completion_rendering	reqlan rq/extension/language/support/features-imports.rq	done	Reference code completion for ideas from other files shows the relative import path in the completion detail. Same-file ideas omit the path detail. [reference_code_completion] [import_code_completion] [import_code_completion_auto_file_import]	0.066
import_code_completion_substring_match	reqlan rq/extension/language/support/features-imports.rq		Filter path candidates by search within the path, not only a starts-with prefix. Typing `path` should match `../../parent/path.rq`. Typing `hellopath` should match `../../hello/inbetween/path/file.rq` ( characters matched in order across path segments ).	0.047
import_does_not_exist_error	reqlan rq/extension/language/support/features-imports.rq		Imports show an underline error when the target file or folder does not exist. Imports also show an underline error when a named imported idea does not exist in the target file. An existing folder is not an error: [import_folder_targets]. CI: ["../../../core_analysis/check.rq".check_unresolved_imports]. [general_errors]	0.151
import_error	reqlan rq/extension/language/support/features-imports.rq	done	" Could not resolve reference " errors offer Quick Fix code actions ( lightbulb and editor right-click Quick Fix ). Fixes: - Add import from a matching idea found in loaded documents or the name catalog pushed from the index - Rewrite the reference to an anonymous qualified form `["path".name]` - Search the index for matching ideas, ideasets, or files ( same `reqlan.searchReference` path as [code_actions] / ["../../host/features-commands.rq".search_code_actions] ), then insert an import - Create the idea in a new. rq file and import it [general_errors] [code_actions] [quick_fixes]	0.078
import_folder_targets	reqlan rq/extension/language/support/features-imports.rq	done	An import path may refer to a folder. A folder is a valid import target when that path exists as a directory. Namespace import of a folder binds the alias to that folder, the same as a file. Extensionless paths still prefer a `.rq` file: [implicit_file_extension]. Related: ["../../../language/imports.rq".import_paths], [import_does_not_exist_error], ["../syntax/features-syntax.rq".file_references].	0.164
remote_imports	reqlan rq/extension/language/support/features-imports.rq		Reqlan files should support importing requirements from remote urls. Remote import syntax should follow import " https://company.com/reqs/style.rq" as styleguide. The extension should resolve, cache, and validate remote imports. Barrel imports should be recommended for token efficiency when many symbols are needed from one remote file.	0.040

Cluster graph

Initialising graph…