Issue 67 - Add callback to return full axe-core results object

[gilgold]

• Adding a callback method for handling the full axe-core results object

[sapegin]

Hey, thanks for the pull request!

This looks like a breaking change. I'm thinking about a new API for the next major release, and probably we'll need to replace all positional arguments of checkA11y with an object because we already have way too many and they are all optional.

I'll keep this pull request as a reference, and either include in the new version or ask you to rebase it on top of it.

[kristina-hager]

I'm thinking about a new API for the next major release, and probably we'll need to replace all positional arguments of checkA11y with an object because we already have way too many and they are all optional.

big plus 1 to using an object for the args.
also, if there will be big changes, i'd suggest just dropping 'violationsCallback' in favor of 'resultsCallback'.
It would be pretty easy for a resultsCallback to focus just on violations.

[sapegin]

That's a good point!

[kristina-hager]

@sapegin - Hi, do you have any ETA for the new API to move to an arguments object? Do you need any help with this?
We are using an internal fork of this lib due to the need for a full results object. We'd rather help out with this version so we can retire our internal fork. Please let me know what can help!
I could, for example, create a PR to move the existing supported options to an args object. That would allow PRs like this and some of the other open ones to rebase and redo their PRs.

[sapegin]

I drafted my ideas on the new API: #75. I hope this covers your use case — let me know what you think.