include .cts files when discovering migrations#1273
Merged
Conversation
WikiRik
approved these changes
Mar 27, 2023
|
🎉 This PR is included in version 6.6.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This was referenced Aug 3, 2024
This was referenced Aug 11, 2024
This was referenced Aug 18, 2024
This was referenced Aug 26, 2024
This was referenced Sep 11, 2024
This was referenced Sep 18, 2024
This was referenced Sep 26, 2024
This was referenced Oct 3, 2024
This was referenced Oct 16, 2024
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.
The migrator currently uses
/^(?!.*\.d\.ts$).*\.(cjs|js|ts)$/to look for migration files. This regex does not include.ctsfiles, which are TypeScripts version of.cjsfiles.Since
.tsand.cjsfiles are already supported, the migrator can include.ctsfiles without further changes.