Skip to content

consider changing imports include name #48

@nilslice

Description

@nilslice

After the recent change in #45, we broke a Tezos example: https://github.com/dylibso/modsurfer/actions/runs/4928214424/jobs/8806287884

This is because the checkfile only has a single import, given that the past semantics of imports.include were such that a module had to have at least the specified imports. Now that we've updated this to mean "the module must have a subset of these imports, but no others", the validation fails for this example.

A consideration would be to change the name from includes here to something less restrictive... maybe allow ?

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