Handle case where parsed config object doesn't have a prototype #365
Conversation
This file contains 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
|
also fixes #314 |
|
The fix uses the minimal safe way of calling hasOwnProperty trick. |
mhamann
approved these changes
May 21, 2021
|
@mhamann When can we expect this fix to be released? |
ilkkao
changed the title
mhamann
pushed a commit
that referenced
this pull request
Jun 21, 2021
|
Available now via https://www.npmjs.com/package/nconf/v/0.11.3 |
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.
Config objects read with
inilibrary 2.0.0 don't have prototype, see: npm/ini@032fbafHandle that case