Skip to content

Targets check not validating implicit imports #127

@fibonacci1729

Description

@fibonacci1729

Consider this wac document:

package test:test targets wasi:http/proxy;

export new spin:kv{...}...;

Where spin:kv is a component that targets the world:

world {
     import fermyon:spin/[email protected];
     export wasi:http/[email protected];
}

Currently, handling implicit instantiation arguments (e.g. the fill via {...} in new spin:kv{...} above) is deferred until encoding. This is a problem because during resolve when the targets predicate is validated we end up ignoring imports that otherwise effect the shape of the composition's world. The above document should fail to validate because the resulting composition contains a superset of the wasi:http/proxy world's imports.

Metadata

Metadata

Assignees

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