paramsForServer Hook

[DaddyWarbucks]

I think we should update the docs to include an example of how one might use the paramsForServer as a hook.

const paramsForServerHook = (...whitelist) => (context) => {
  context.params = paramsForServer(context.params, ...whitelist);
  return context;
};

I am not a fan of having to use the paramsForServer on every service call and would rather have it work more generically via a client side hook.

I can update the docs at some point, but wanted to capture my solution.

[fratzinger]

I would go a more drastic way. We should deprecate the current paramsForServer util and add a paramsForServerHook and advertise it as the new way to go.

In a next major release, I would like to rename the paramsForServer util to paramsForServerUtil.
And in another major release I would like to rename paramsForServerHook to paramsForServer.

[daffl]

Here is a question, what do the params hooks do differently than something like this?

async (context) => {
  const { myParam, ...query } = context.params.query || {}

  context.params = {
    ...query,
    myParam
  }
}

[fratzinger]

Just a quick headsup. I started working on a massive rewrite of the package (#764). It's not released yet and will take a few weeks.

This is what I came up with:
https://github.com/feathersjs-ecosystem/feathers-hooks-common/blob/modernize/src/hooks/params-for-server2/params-for-server2.ts
https://github.com/feathersjs-ecosystem/feathers-hooks-common/blob/modernize/src/hooks/params-from-client2/params-from-client2.ts

I wrote these in my package 'feathers-utils' and use them for months. Porting them over to hooks-common. I deprecated the old paramsForServer & paramsFromClient.