- Notifications
You must be signed in to change notification settings - Fork14
Emit null instead of empty object forvalidateAshHooks#81
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Uh oh!
There was an error while loading.Please reload this page.
This was left to minimize report.json changes in earlierrefactoring. Fixing it now should only affect the report.jsonstructure but not report.html.
validateAshHooksfoolip commentedDec 16, 2019
I've trimmed this PR to only the remaining TODO. |
dontcallmedom commentedDec 16, 2019
The diff shows which I don't understand and wouldn't have expected. Any insight? |
foolip commentedDec 16, 2019
Oh, I didn't anticipate this, but it's because of this logic: Lines 55 to 61 in39443ae
@dontcallmedom maybe this should be changed to always use the object form? If such a change is landed first, this change should then be a no-op. |
dontcallmedom commentedDec 16, 2019
changing to always use object form makes sense to me, but will probably need changes in downstream usage of the JSON results (which points toward the need of setting up a JSON schema for the results I think) |
foolip commentedDec 16, 2019
As it happens I was just working on using a JSON schema to validate w3c.json, if that works out it should be straightforward (ish) to use it for report.json as well. Let's leave this PR hanging, it's not urgent in any way. |
Uh oh!
There was an error while loading.Please reload this page.
This was left to minimize report.json changes in earlier
refactoring. Fixing it now should only affect the report.json
structure but not report.html.