reverse migration downQueries #12
Merged
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
jkillian
approved these changes
Nov 20, 2025
jkillian
reviewed
Nov 20, 2025
| name: migrationName, | ||
| upQueries: sqlInMemory.upQueries, | ||
| downQueries: sqlInMemory.downQueries, | ||
| downQueries: sqlInMemory.downQueries.reverse(), |
There was a problem hiding this comment.
Is it okay to do this in place? Or do we need toReversed()?
Contributor
Author
There was a problem hiding this comment.
I think it's ok since the original code did a reverse(), and unfortunately the TS build for the project is not using a recent enough lib setting to use toReversed() :(
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.
Whoops, while refactoring for #11 I dropped the reversing of
sqlInMemory.downQueries