Enable chaining for middlewares and afterwares in the network interface - Issue 564

[ghost]

TODO:

• If this PR is a new feature, reference an issue where a consensus about the design was reached (not necessary for small changes)
• Make sure all of the significant new logic is covered by tests
• Rebase your changes on master so that they can be merged easily
• Make sure all tests and linter rules pass
• Update CHANGELOG.md with your change
• Add your name and email to the AUTHORS file (optional)
• If this was a change that affects the external API, update the docs and post a link to the PR in the discussion

[ghost]

Hi,
I'm trying to solve #564. Have a look at this PR and tell me what you think.
Remarks :

1. If I'm not mistaking, it should also possible to chain use() and useAfter() in the same call. I might need to also add a test for that. Right now, my patch only tests use(...).use(...) and useAfter(...).useAfter(...). Please tell me if such test is relevant.
2. As this PR adds a new feature, I need to update the docs. I will, but first I'd like to know if the PR looks good.

Regards

[helfer]

Looks great, thanks a lot! Just one tiny change requested.

[helfer]

Can we simplify this to "Enable chaining of use and useAfter function calls in network interface"?

[ghost]

Just added a new commit that includes the required change + two new tests for testing use(...).useAfter(...) and useAfter(...).use(...) chaining.
I will now work on a PR on the docs. Stay tuned ...

[ghost]

Here is a link to a PR on apollostack/core-docs which documents this feature :
https://github.com/apollostack/core-docs/pull/218

[ghost]

For me, this PR is ready to be merged but tell me if some changes need to be done.

[helfer]

Looks good to me. Thanks a lot @oricordeau !