Skip to content

Support custom persist and hydrate callbacks for primitive types. #24

Description

@solid-yuriiprykhodko

As pointed out by @solid-vovabeloded:
Currently if we use HydratedSubject with a primitive type, custom persist and hydrate callbacks won't be invoked, or used at all:
image

The idea is to change the check order in the above method to use the custom callbacks, if they were provided, and then fall back to standard handling.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions