CLI: Disallow self-references for storage layout validations #1067
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
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.
Fixes #1064
Disallows self-references when using the
--referenceoption or the@custom:oz-upgrades-fromannotation.NOTE: This is technically a breaking change, but we should not bump the major version for this release. I consider this as a bug-fix, since the previous behavior of allowing self-references would defeat the purpose of storage layout validations.
If users really cannot provide a reference, either in the same project or in a previous build info file, then they should skip storage layout validations as a last resort. This is described in the new error message that we throw.