-
Notifications
You must be signed in to change notification settings - Fork 52
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
Updating result schema to include more specific data #217
Conversation
Co-authored-by: Robert Jackson <me@rwjblue.com>
Co-authored-by: Robert Jackson <me@rwjblue.com>
@scalvert Would you please post a sample result, so we can compare/contrast what will be audited out with this change? |
@MelSumner sure thing. I've added a sample output. Additionally, the TypeScript interface effectively gives you a sense of the format of the output. Essentially, we've trimmed out a bunch of extraneous data that would unnecessarily bloat the output without immediate value. Some of the outer information in a single
When running tests on a small sized project, this extra data would likely not be too large. On any reasonably sized project, this data would likely grow quite large. |
@rwjblue @MelSumner any more updates/feedback/issues with this PR? I'd like to get it shipped soon so we can target it for a new release. |
The results that are returned from each failed audit are quite large. When considering the size of the payloads passed through the middleware, passing raw
AxeResults
objects could result in a very large payload. This PR specifically reduces the size of the overall payload that's sent through the middleware, which will also reduce the size written to disc.In addition to this, there's extra data that's useful to gather when assessing audits, such as
The stored result, per test, adheres to this interface:
JSON result example