Support hooks

[PaperStrike]

Motivation and Context

With hooks, you can now change the request, response, parsed document (of type Document), and DOM switchesResult (of type SwitchesResult) used inside Pjax.

Inspired by falsandtru's sequence option.
Thanks to @Yahav for the introduction.

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Refactor (no bug fix and new feature but improvements)

Checklist:

• My change requires new tests.
• I have added tests to cover my changes.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.

[Yahav]

How about a hook after the blocking javascript is done executing as well?

[PaperStrike]

How about a hook after the blocking javascript is done executing as well?

Could you please give me some use cases for this?

[PaperStrike]

This package not only cares about the functionalities, but being small and compliant with the standard. There isn't an event for something like "all script initial execution done" in the initial page load, maybe it's for security or it's simply meaningless, so I prefer not to have it as for now (load event is a different case as it indicates all the resources). So if you could provide a reasonable use case for this, that would really help.

[Yahav]

Well, in my case i would use it to register some components, which i can do only once they have finished initializing themselves.
But i see your point, i might need to fire some events from within those scripts for this kind of functionality.

[Yahav]

Can you please merge this?