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
deep nested keys not pulled out correctly via method call approach #2
Comments
I wrote some tests, and I can't duplicate the issue. Want to write in your own tests and see if you can do it? Check this out: http://github.com/binarylogic/settingslogic/commit/e9271139c5a0d7f93b7406a98c8d8019a374263d |
the ambiguity is when two child keys have the same value I forked and made a test, http://github.com/ak47/settingslogic/tree/master here's what I get andy@pdd-andy-mbp (master)->spec spec/settingslogic_spec.rb 'Settingslogic should access other extra deep nested settings' FAILED Finished in 0.044861 seconds 8 examples, 1 failure it sets the child key name as a method, the one that gets set first has that method name to return it's value example from above yml,
it doesn't matter what precedes the 'qa' call |
I was having the same issue. Can't use the new version |
I pulled in some changes to fix this. Thanks. |
when parsing multiple yml files. use merge instead of replace.
example yaml,
development:
bucket:
master:
pr: pcdlnv-mstr-dev
qa: pcdlnv-mstr-dev-qa
manifest:
pr: pcdlnv-mfst-dev
qa: pcdlnv-mfst-dev-qa
message:
pr: pcdlnv-msg-dev
qa: pcdlnv-msg-dev-qa
now in script/console
when calling the value using the dotting method it gets the wrong value, but using Hash key is correct
The text was updated successfully, but these errors were encountered: