fix: sequelize latest #232
Merged
Conversation
This file contains 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
papb
reviewed
Jul 5, 2020
| const describeModel = (model: any) => | ||
| model.describe().then(d => { | ||
| // FIXME [sequelize@>=6] remove this hack when only sequelize>=6 is supported | ||
| Object.keys(d).forEach(k => delete d[k].unique); |
There was a problem hiding this comment.
We're asserting in a few places on the output of this function. The new version of sequelize includes an extra property unique. So that tests pass for old and new sequelize, this deletes it.
papb
approved these changes
Jul 5, 2020
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.
sequelize@nextno longer seems to exist - this switches CI over tosequelize@latest.