Skip to content

Automatic migrations should not trigger for dependencies #8096

@zth

Description

@zth

It seems that automatic migrations can trigger for dependencies. Case in point: @rescript/react uses the deprecated Js.Nullable.t. This triggers a warning about deprecation (and migration of that), but in a weird broken loc, and that obviously can't be applied since deps can't be rewritten/migrated.

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