Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Polywrap Manifest: Make use of defaults #1909

Closed
krisbitney opened this issue Sep 18, 2023 · 0 comments · Fixed by #1911
Closed

Polywrap Manifest: Make use of defaults #1909

krisbitney opened this issue Sep 18, 2023 · 0 comments · Fixed by #1911
Assignees

Comments

@krisbitney
Copy link
Contributor

Manifest: Make use of defaults

When it comes to developing a wrap, the user needs to define a polywrap.yaml manifest; in this manifest is necessary that the module and schema are defined. This actually may be simplified. The user should not need to define those unless it has some custom name or path (which is actually very rare).

We need to implement defaults per language and make the build process smart enough to find the needed files if not given

Today's Devexp

format: 0.5.0
project:
  name: asyncify
  type: wasm/rust
source:
  schema: ./polywrap.graphql
  module: ./Cargo.toml

Tomorrow's Devexp

format: 0.5.0
project:
  name: asyncify
  type: wasm/rust
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant