…te everyauth.enabled Object to keep track of which modules have been activated.
…ject received from the OAuth provider into Error instances.
…le name (before, only included a step name).
…her values nor a Promise is returned by the step's function.
…ect if a querystring is sent back instead of a JSON object.
…ts string args into Error instances.
…as they are started and completed => Easier to pinpoint which step a potential bug appears.
… easier to write OAuth2 submodules. Less reliance on the `oauth` npm module, which makes too many non-configurable assumptions about what is sent by mandatory to the OAuth provider.
…t a JSON object in github module.
…on-configured configurables. Renamed oauth module oauth2 module.
…s the ordered step names, not the module. MatSeq is also created upon route declaration, not later on lazily. Finally, added introspection methods for listing the routes and each route's steps (all, incomplete, and invalid).
…ence#checkSteps, so that an Error is thrown at startup for non-defined step logic.
…epts and promises) and that the parameters a step accepts have been promised by prior steps. Otherwise, errors are thrown.
…as not been configured yet.
…e can detect which step fails, instead of arbitrary hanging of the program -> better debugging.
…timebacks to Promise.
…efinit` method (so we can add `super()`).
…ure strategy for storing routes, steps, and their relationships.