This repository has been archived by the owner on Oct 30, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 214
Allow the same context to be used multiple times in configuration #1254
Comments
Should the last one take precedence, or merge over an earlier one? The merge allows a particular context to be "built up" from multiple files. (Alas, merging arrays is problematic.) |
merge over = take precedence. I don't see the difference... |
I guess I was trying to make a distinction between "replace" and "merge". You seem to have been thinking of "merge" too, so I think we have the same idea 😄. |
Can we prioritize this request? We would like to have it by the end of November/early December. Thanks! |
bumping this into trello board: https://trello.com/c/XYLOloRT/768-search-gh-1254-allow-the-same-context-to-be-used-multiple-times-in-configuration |
lzhan
pushed a commit
to lzhan/mojito
that referenced
this issue
Nov 18, 2013
…e times in configuration
lzhan
pushed a commit
that referenced
this issue
Nov 20, 2013
fix issue #1254 Allow the same context to be used multiple times in configuration
Available in mojito 0.8.1. |
lzhan
pushed a commit
to lzhan/mojito
that referenced
this issue
Dec 23, 2013
…e times in configuration
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Our application configuration is spread across multiple files (we use the "applicationConfigFiles" directive to include additional configuration files into our main application.yaml...) Unfortunately, when the same context is specified multiple times, e.g. "runtime:server,lang:fr-FR", mojito throws an error:
Because the order matters in the "applicationConfigFiles" directive, we should be allowed to use the same context multiple times. If the same configuration setting is set multiple times, the last one should take precedence...
The text was updated successfully, but these errors were encountered: