Configuration file
axic opened this issue · 5 comments
axic commented
From the README:
The configuration file starts with a ruleset entry, where the name can be anything. Inside the ruleset are its options.
ewasm:
- file: "target/wasm32-unknown-unknown/release/sentinel.wasm"
- remapimports:
- style: ewasm
- deployer
axic commented
runevm:
- input: "target/wasm32-unknown-unknown/release/runevm.wasm"
- remapimports:
- preset: ewasm
- deployer
sha256:
- input: "target/wasm32-unknown-unknown/release/ewasm_precompile_sha256.wasm"
- output: "sha256.wasm"
- remapimports:
- preset: ewasm
jakelang commented
My proposed format:
ruleset:
- file: "file.wasm"
- module:
- name: "remapimports"
- preset: "ewasm"
- module:
- name: "deployer"
jakelang commented
@axic Actually I would rather not prepend all the elements of the ruleset with hyphens, because to the parser it becomes a list of child mappings with one entry, rather than a child map.
jakelang commented
Closing this, as it is implemented. A new issue can be opened for generalizing the YAML config format.
axic commented
I don't think it is implemented, until the PR is merged.