Test suite: Add $schema to scenarios, drop expCleanSrc
#827
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
It's not (or not just) lack of consensus. We don't have a normative requirement here. |
aphillips
approved these changes
Jul 15, 2024
|
fast-track per 2024-07-22 call. @mradbourne please review |
mradbourne
approved these changes
Jul 23, 2024
There was a problem hiding this comment.
Looks great.
You can also remove test/.vscode/settings.json, which will be redundant after this change.
|
Fast track criteria were met. Thanks all! |
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.
Two different changes here:
$schemaproperty to each scenario file, so that they can get autocompletion & validation automatically in editors.expCleanSrcvalue from tests, as we don't have consensus on the canonical representation of each message.