[Blueprints] Rename Blueprints v1 types, add Blueprint v2 types #2648
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
adamziel
added
[Type] Enhancement
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.
Motivation for the change, related issues
Renames Blueprint v1-related types an explicit "v1" in the name. Declares Blueprint v2-related types such as the schema from the proposal.
A part of #2586.
Breaking changes
This is a breaking change with respect to TypeScript types. The type named
Blueprintnow meansBlueprintV1 | BlueprintV2which is a broader type than before. Therefore, let's do a major version bump after merging this PR. There are no breaking changes in runtime. cc @brandonpaytonTesting Instructions (or ideally a Blueprint)
CI