Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tokenization occurs both on create and update regardless of config #19

Open
nishimura-d opened this issue May 31, 2021 · 0 comments
Open

Comments

@nishimura-d
Copy link

In "Usage" section of README, 2 cases are described:

  • To tokenize the password column on updates, add this to your UsersTable:
  • If instead you wanted to have it create a token both on account creation and credentials update:

But actually tokenization occurs on create in 1st config.
implementedEvents config has no effect.

This is because the return value of Behavior::implementedEvents() has Model.afterSave if afterSave() method exists.
Maybe own implementation of TokenizeBehavior::implementedEvents() is needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant