Skip to content

Change hooks to check against null when no hook is specified #51

Description

@evanplaice

Currently, false is used as the value to indicate that a hook hasn't been set.

This can and will cause conflicts with user-defined hooks that use false as a return value for their particular use case.

This is an API breaking change so it should be included in the next major release.

Ref: #44

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions