Skip to content

Should binary WIT packages have imports in their config? #29

@ouillie

Description

@ouillie

This is a design question. When parsing a binary WIT package, the exports are populated, but the imports are always empty. AFAICT, this is because a WIT packages don't technically import anything because they are not component implementations. They are just interface definitions. But by that same logic, they don't technically export anything either. So I'm confused as to why the exports are populated while the imports are not.

I think it would make sense to list the imports.

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