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

Fix configuration not always using resource scope #446

Merged
merged 1 commit into from Jan 7, 2019

Conversation

Projects
None yet
2 participants
@LaurentTreguier
Copy link
Contributor

LaurentTreguier commented Jan 2, 2019

When requesting a nested configuration section (e.g. a.b.c), the configuration returned isn't scoped to the requested uri, although it does so when requesting something like a, with no dot inside.

Fix configuration not always using resource scope
When requesting a nested configuration section (e.g. `a.b.c`), the configuration should still be using the `resource` scope, and act the same as when requesting a more global configuration section (e.g. `a`).
@dbaeumer

This comment has been minimized.

Copy link
Member

dbaeumer commented Jan 7, 2019

Good catch. Thanks !

@dbaeumer dbaeumer merged commit efd996d into Microsoft:master Jan 7, 2019

2 checks passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
license/cla All CLA requirements met.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment