David Luecke

We have been trying to do this in https://github.com/feathersjs/feathers/pull/2665 for the Feathers core packages but so far have not gotten it to work.

The most straightforward approach I'm seeing would be to update the configuration type with the settings that are being use. So here something like: ```ts type AppConfig = { configuration:...

Feathers does not make a copy of your data so if you modify them (e.g. in a hook) it is a reference to the same data that you originally passed....

Mind you, I totally agree that `hashPassword` should do exactly that (which it seems it does not)!

That would totally work. But yes, any object you pass will stay the same. There is a similar discussion in https://github.com/feathersjs/feathers/issues/675. I think you are right and making a copy...

It currently does not. A discussion around this can be found in https://github.com/feathersjs/socketio/issues/37

That service you are suggesting is actually pretty neat. I sometimes also just create a separate service for the join table model. I wonder if @DesignByOnyx has any insights here...

I also think Sequelize makes this a little more difficult than it needs to be. The model methods seem intuitive as a developer but from an API client perspective you...

Did you [register](https://docs.feathersjs.com/api/authentication/service.html#setup) the `system` strategy as another `localStrategy` instance? ```js authService.register('system', new LocalStrategy()); ```

Unfortunately, unless this has been fixed in a later release, upgrading to socket.io 3 will break _every_ existing client in the worst way possible in that requests just get stuck...