I stumbled on a bug in the npx feathers generate authentication command.
I ran npx feathers generate authentication with the following options:

Pay attention to the value for What is your authentication service name?. It is set to users and not user.
This led to me getting the following errors in src\services\users\users.schema.ts

My guess is, that the user part in context.params.user is hardcoded, but it should be inferred from the answer to the What is your authentication service name? question.
This bug can be reproduced by:
- running
npx feathers generate authentication
- entering anything other than "user" for the
What is your authentication service name? question
For completeness' sake, this is the config I used to setup feathers with:

I stumbled on a bug in the
npx feathers generate authenticationcommand.I ran

npx feathers generate authenticationwith the following options:Pay attention to the value for
What is your authentication service name?. It is set tousersand notuser.This led to me getting the following errors in

src\services\users\users.schema.tsMy guess is, that the
userpart incontext.params.useris hardcoded, but it should be inferred from the answer to theWhat is your authentication service name?question.This bug can be reproduced by:
npx feathers generate authenticationWhat is your authentication service name?questionFor completeness' sake, this is the config I used to setup feathers with:
