-
Notifications
You must be signed in to change notification settings - Fork 408
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
Decouple configuration from assets #213
Decouple configuration from assets #213
Conversation
unless @_options? | ||
@_options = $('body').data('kandan-config') | ||
@_options.nowThreshold = 3000 | ||
@_options.timestampRefreshInterval = 2000 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you think about adding these 2 settings to the Kandan::Config so we can have all settings in one place?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup, sounds like a good idea. 👍
You can rebase this once we merge #212 and I'll merge it |
rebase this and ill merge it |
…ng, removing the coupling between rendered assets and the backend application configuration in place at time of rendering.
…l for consistency.
Haha, was already on it. 😁 |
…m-assets Decouple configuration from assets
🚢 'ed |
…ation-from-assets Decouple configuration from assets
This PR contains changes that remove the need for .coffee.erb files in the assets, allowing the server configuration to be modified without needing the assets to be regenerated.
ie. removing the tight coupling between the configuration/environment at the time the assets are generated and the generated frontend application.