Skip to content

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

@nishimura-d

Description

@nishimura-d

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions