feat: Update schema to support variable autoupdate urls #5297
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.
Description
Before, any
autoupdate
url
had to take the form of a well-formed URI. However, this would throw an error for otherwise-functional urls using variables fromcheckver
that didn't match this schema. Example: (note how$matchUrl
will be a valid URL when evaluated, but as a literal string it is not a valid URL)Motivation and Context
Closes #5296
Closes #5158 (probably a dupe, but not 100% sure)
How Has This Been Tested?
I have a
.json
file that shows a warning in VSCode when pointing to the old schema. I pointed my VSCode to the new schema by modifying.vscode/settings.json
. The error on myurl
went away. No new warnings showed up on my other existing packages.Checklist:
develop
branch.