Rework

I was thinking about whether we should rework the repo. I have two suggestion in mind.

1. Moving the source code to a TypeScript base. I would argue this is more maintainable and this would also help with intellisense in various IDE’s.

2. This is more radical - Moving away from actions in data and instead use authmanagement/{action} . So a reset password would move from

{
    "action": "resetShortToken",
    "data": { ... }
}

To a more REST like approach with /authmanagement/reset This would make it work more like a REST API and as well as a standard feathers service.

I realize this would be breaking changes, but I think it would benefit the overall structure of calling the API

Let me know what you think, and if I should elaborate.

[fratzinger]

first official typescript release:

npm i feathers-authentication-management@pre

also checkout https://feathers-a-m.netlify.app/ for the new docs made by @OnnoGabriel 🎉. The release aims to have no breaking changes at all. But it also has a lot of new things. Every action is now callable in three ways:

1. old traditional way
2. through a separate service like: app.use('auth-management/password-change', new PasswordChangeService(app))
3. through custom methods: app.service('authManagement').passwordChange(...) (in preparation of feathers v5)

Option 2 and 3 also have a flattened data argument. Please see the comparison:

const { AuthenticationManagementService } = require('feathers-authentication-management');

app.use('auth-management', new AuthenticationManagementService(app, options));

app.service('auth-management').create({
  action: 'passwordChange',
  value: {
    user: identifyUser, // identify user, e.g. {email: '[e-mail]'}. See options.identifyUserProps.
    oldPassword, // old password for verification
    password, // new password
    notifierOptions: {}, // optional - an object passed to notifier function
  },
}

const { PasswordChangeService } = require('feathers-authentication-management');

app.use("auth-management/password-change", new PasswordChangeService(app, options));

app.service('auth-management/password-change').create({
  user: identifyUser, // identify user, e.g. {email: '[e-mail]'}. See options.identifyUserProps.
  oldPassword, // old password for verification
  password, // new password
  notifierOptions: {}, // optional - an object passed to notifier function
}

I think once we ship the pre-release as an official release, we can close this issue. What do you think? Is there anyone who’s willing to test out the new pre release?

[MohammedFaragallah]

@cantoute please see example