Skip to content

replace equality check with bulletproof solution #13

@cpeddecord

Description

@cpeddecord

This issue has hamstrung certain aspects of local development vis a vis:

  • npm link would cause multiple instances of Immutable to be referenced
  • working within a mono-repo tooled by Lerna causes multiple instances of Immutable to be referenced

Could this be solved using something like Immutable.Map.isMap() vs. comparing constructors?

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