Add --only-preserve-backend flag to lamdera check#93
Open
MavenRain wants to merge 1 commit intolamdera:lamdera-nextfrom
Open
Add --only-preserve-backend flag to lamdera check#93MavenRain wants to merge 1 commit intolamdera:lamdera-nextfrom
MavenRain wants to merge 1 commit intolamdera:lamdera-nextfrom
Conversation
When set, the generated migration file uses ModelUnchanged/MsgUnchanged for all types except BackendModel, which gets the normal auto-generated migration. Useful when iterating on frontend types without caring about their migration continuity. Fixes lamdera#66.
miniBill
reviewed
Apr 1, 2026
| migrationModuleText = T.concat ["Evergreen.Migrate.V", show_ newVersion] | ||
|
|
||
| typeDidChange t oldHash newHash = | ||
| oldHash /= newHash && not (onlyPreserveBackend && t /= N.fromChars "BackendModel") |
Member
There was a problem hiding this comment.
We probably also want BackendMsg here?
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.
When set, the generated migration file uses ModelUnchanged/MsgUnchanged for all types except BackendModel, which gets the normal auto-generated migration. Useful when iterating on frontend types without caring about their migration continuity. Fixes #66.