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

Priority order seems to be the wrong way around #70

Closed
Licenser opened this issue Nov 15, 2013 · 2 comments
Closed

Priority order seems to be the wrong way around #70

Licenser opened this issue Nov 15, 2013 · 2 comments

Comments

@Licenser
Copy link
Contributor

in my tests a 01- file overwrites a 00- file and a 99- one overwrites a 01- one.

@Licenser
Copy link
Contributor Author

To make this more interesting:

00.schema

  • define setting_form_01 as setting_form_00 (to overwrite it)

01.schema

  • define settingr_form_01 as setting_form_01

99.schema (its the same as 00)

  • define setting_form_01 as setting_form_00 (to overwrite it)

Generate config it looks like:

setting_form_00 = bla
setting_form_01 = blubb

The expected value from setting_form_01 would be bla since setting_form_00 should over write it. Sad story, it's blubber.

More experiment!

Remove 00.schema (but leave the generated config). Outcome is bla what why?

Regenerating the config with only 01 and 99 reverses the order so it makes it look like:

setting_form_01 = blubb
setting_form_00 = bla

@joedevivo
Copy link
Contributor

covered in #73, closing

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

No branches or pull requests

2 participants