feat(jsii-diff): remap old to new FQNs #4976
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
Add a new feature: remapping of FQNs. This allows proper API compatiblity checking of `jsii-diff` even if types get moved around. Now normally you shouldn't move types around because it breaks backwards compatibility anyway, but in case you did and you want a handle not not accidentally changing other things, you can confirm it with this feature.
mrgrain
approved these changes
Nov 7, 2025
Contributor
|
Thank you for contributing! ❤️ I will now look into making sure the PR is up-to-date, then proceed to try and merge it! |
Contributor
|
Merging (with squash)... |
Contributor
|
Merging (with squash)... |
This was referenced Nov 19, 2025
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.
Add a new feature: remapping of FQNs. This allows proper API compatiblity checking of
jsii-diffeven if types get moved around.Now normally you shouldn't move types around because it breaks backwards compatibility anyway, but in case you did and you want a handle not not accidentally changing other things, you can confirm it with this feature.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.