docs(rfd): Draft root-qualified extends paths - #1020
Open
JeanMertz wants to merge 1 commit into
Open
Conversation
`config_load_paths` resolves against the workspace root while `extends`
resolves against the declaring file's directory. That asymmetry means a
higher-precedence config root cannot address a file in the workspace,
so settings that must load on every invocation have to be inlined into
the user-workspace config, away from the rest of the project's config
and outside version control.
The draft proposes an optional `root` qualifier on an `extends` entry,
naming the config source its path is anchored to. Omitting it preserves
today's behavior exactly.
Filed as a draft rather than a proposal for discussion: the same file
is already reachable through an external access grant, so this is an
ergonomics gap rather than a capability gap, and it overlaps with
RFD D35, which coins the same `{ root, path }` shape for a different
purpose.
Signed-off-by: Jean Mertz <git@jeanmertz.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
config_load_pathsresolves against the workspace root whileextendsresolves against the declaring file's directory. That asymmetry means a higher-precedence config root cannot address a file in the workspace, so settings that must load on every invocation have to be inlined into the user-workspace config, away from the rest of the project's config and outside version control.The draft proposes an optional
rootqualifier on anextendsentry, naming the config source its path is anchored to. Omitting it preserves today's behavior exactly.Filed as a draft rather than a proposal for discussion: the same file is already reachable through an external access grant, so this is an ergonomics gap rather than a capability gap, and it overlaps with RFD D35, which coins the same
{ root, path }shape for a different purpose.