feat: structural provider provenance via meta.provider#399
Merged
sini merged 1 commit intodenful:mainfrom Apr 8, 2026
Merged
Conversation
Provider path tracking now lives in meta.provider instead of __provider. providerPrefix threads through provides submodules and mkAspectsType sets namespace roots.
Member
|
Flawless! Please merge this yourself when you accept the maintainer invitation. |
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
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.
Summary
How it works
The provides submodule extends providerPrefix with the current aspect's name before passing it to child provider types. Namespaces set providerPrefix = [ name ] as their root. den.provides uses [ "den" "provides" ]. Top-level aspects default to [].
This lets adapters distinguish "bar provided by foo" from a top-level "bar" by inspecting aspect.meta.provider.