-
-
Notifications
You must be signed in to change notification settings - Fork 212
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
Variable expansion support for @Key #69
Comments
taking a quick peek at the source it looks like this is pretty easy to implement, just calling expandVariables on the result of expandKey in the resolveProperty method of the PropertiesInvocationHandler |
Yes. This is very useful and it's already implemented on I wrote the documentation today so I closed the related issue #63 There is already the unit tests for it, so it should work fine. See the related docs for additional infos. Last paragraph has been added today, and it is specific to this issue you spotted. |
Let me know if you need something more, related to this, or if the feature I implemented for issue #63 covers your usage pattern, so I can close this issue. Thanks. |
#63 looks exactly like what I was looking for (sorry for not looking before posting =/ ) Appreciate the quick response, thanks for the great work! |
Thanks.
No worries at all. |
@key("myapp.${webappContextName}.jdbc.url")
Then I could create a new ConfigFactory passing in the webappContextName as a property and get a new jdbc url for each instance of my webapp. That'd be pretty neat.
The text was updated successfully, but these errors were encountered: