Feedback about page 'plugins-reference/plugins-features/adding-pipes.md'

[Tyki]

That's not an issue, but a feedback from an user. It would be amazing to have an example showing all the different possibilities to do on the incoming request and on the outgoing response.

Actually, the "Listen Synchronously" just show how to modify the response. Since there are events like "http:*" and "request:onSuccess", it would be to have a decent list of differents actions that are possibile at this specific moment in the lifecycle of the request.

That would allow the integrator to see what he can do with pipe & hooks

[Aschen]

It's a very good idea !
Can you be more explicit about some of your use cases ? We are currently rethinking to design of the plugin system and make it more developer friendly.
All help is welcome :)

[Tyki]

Since there is a cookbook about elasticsearch, my suggestion would be to be able to produce some example for all basic cases (a few that came to my mind) :

• Create a pipe/hook (already done)
• Modifying the request by doing some stuff in the database (removing / adding data to the answer)
• Log errors from a 'onError' with a specific hook (to show the subtility between pipe and hook)
• Do some basic authentication examples with http:get and http:post and cookie
• Modify the local strategy (going from email/password to kuid/password, we have this also)
  and more (maybe take the list of events triggered and do a brainstorming around some basic functionalities that you may have everyday)

Would be good to give a CLI a second life, with tools to generate plugins to get the basic skeleton for dependant plugins types (protocol, auth, controler etc)