-
-
Notifications
You must be signed in to change notification settings - Fork 7.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set schema for manifest #2099
Set schema for manifest #2099
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ln980 was added in cc95d4e and ln2268 in 1b14b88, both of #2068. The errorMsg str lists of those two items are somewhat vague and don't always have an impact, and it's possible that someone would remove one thinking that it's no longer needed. Sorta like how YouTube gave us completely different results depending on region --- something that not everyone would pick up on in a quick test |
huh. now that you mention it, those two lines are not compliant with the schema... time to update |
Updated so that mixed error values are flagged. i.e. Leaving an errorCode present while errorType is set to message would be yellow-lined. |
Nothing major here.
Sets the schema for data[.]json to allow for autocomplete, validation, etc. Reduces the likelihood of things being missed or left behind.
Setting the schema happened to uncover a couple minor instances of this (old username_unclaimed, noPeriod, etc). Those have been cleared.
I may adapt this in the future to disallow keys such as errorMsg when they don't match their dependent errorTypes, but that's a later problem.Done.Looks like this was also mentioned back in #1336 and #1338. (so, closes #1336, closes #1338, if merged)