Improve runtime compatibility checking logic. #99
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.
This PR is to improve the
substrate-differ
to detect more compatibility changes and improve the reported changes.OldWeight(pub u64)
->u64
)At Polymesh we added a metadata checker to our CI pipeline to help us spot Breaking API changes:
https://github.com/PolymeshAssociation/Polymesh/tree/develop/metadata-tools
It is using the
substrate-differ
from this PR.Here is an example output from one of our PRs. Note the
NOT COMPATIBLE
that are used to help trace where a breaking change happened. There is also aREQUIRES TX VERSION BUMP
marker to help find where a TX breaking change happened, but this report doesn't have a tx API change.