Fix Specification of input.json #2710
Merged
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
abraemer
force-pushed
the
abraemer-fix-readme
branch
2 times, most recently
from
dee3dfc to
eaf6bf8
Compare
Per the schema the field `frequentLicenses` is not required.
abraemer
force-pushed
the
abraemer-fix-readme
branch
from
eaf6bf8 to
5af3974
Compare
mstykow
approved these changes
Jan 10, 2025
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.
Summary of changes
moved
frequentLicensesto the optional section of the specification ofinput.json. Also converted to camel case to match the schema.Context and reason for change
Per the schema the field
frequentLicensesis not required.