Added setters as an option instead of hardcoded variables.#31
Open
bytestream wants to merge 1 commit into
Open
Added setters as an option instead of hardcoded variables.#31bytestream wants to merge 1 commit into
bytestream wants to merge 1 commit into
Conversation
|
Hey there, why wouldn't you just put it into .gitignore and generate it separately for each separate environment? |
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
2 participants
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.
It was becoming painful to commit the routes js file to our git repo as the root URL would often change between developers.
This basically adds the option to generate a blank javascript file, without any of the configuration variables being hardcoded. You can then set the variables at run time as appropriate