Don't regenerate pruned codegen modules in 'test:gen'#215
Closed
adamdicarlo0 wants to merge 1 commit intowolfadex:mainfrom
Closed
Don't regenerate pruned codegen modules in 'test:gen'#215adamdicarlo0 wants to merge 1 commit intowolfadex:mainfrom
adamdicarlo0 wants to merge 1 commit intowolfadex:mainfrom
Conversation
Elm Pages will run `elm-codegen install` unless we set an env var telling it not to do so.
9ec217d to
acfd124
Compare
Contributor
Author
|
This is unnecessary with #214, and will conflict with it, so I'm going to close this. |
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.
Elm Pages supports an env var to skip running
elm-codegen install.Without this, any time I run
npm run test:genlocally, I get a very dirty git tree with all theGen.modules recreated.