Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support dots in resolver names for namespaces #539

Closed
odelalleau opened this issue Feb 11, 2021 · 0 comments · Fixed by #542
Closed

Support dots in resolver names for namespaces #539

odelalleau opened this issue Feb 11, 2021 · 0 comments · Fixed by #542
Assignees

Comments

@odelalleau
Copy link
Collaborator

odelalleau commented Feb 11, 2021

Is your feature request related to a problem? Please describe.

Introducing new resolvers in libraries may clash with user-defined custom resolvers.

Describe the solution you'd like

Supporting dots in resolver names to denote namespaces would avoid such clashes, e.g., env could become oc.env (although this specific change to the env resolver is not part of this issue).

Nested namespaces will also be supported (ex: ${ns1.ns2.func:123}).

Describe alternatives you've considered

Also considered _.

Additional context

Related to discussion in #383 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants