Added option cache_templates to keep compiled template in memory (for Rails integration)#46
Merged
Conversation
… Rails integration)
fterrazzoni
force-pushed
the
railscache
branch
from
bc0a2f7 to
1a73fb3
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
If this option is enabled, BABL's Rails integration keeps all compiled templates in a cache forever. It noticeably improves performances, and this difference will become much more significant when code generation will be available.
Notice that only Rails integration is impacted by this setting. There is no other caching mechanism in BABL anywhere else.