Latest Meteor build 0.8.0 has RELOAD_SAFETYBELT token needs parsing #52
Conversation
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
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.
In Meteor base app.html file in latest Meteor build 0.8.0, RELOAD_SAFETYBELT token has been added for parsing on application startup and with server.js occupying that function in pipeline token is not being parsed and displays on page. Still not sure why Meteor webapp.js is not parsing tokens and must be implemented here but this is the fix in conjunction with the previous HTML_ATTRIBUTES and RUNTIME_CONFIG parsing logic.
RELOAD_SAFETYBELT first implemented in commit: meteor/meteor@2760346