CLI - Remove deprecated use of the `--project-path` flag

Open bfops opened this issue 1 year ago • 1 comments

Description of Changes

Remove a deprecated --project-path flag.

API and ABI breaking changes

If this is an API or ABI breaking change, please apply the corresponding GitHub label.

Expected complexity level and risk

Mar 01 '24 22:03 bfops

(do not merge until we're ready to make this breaking change!)

Mar 14 '24 20:03 bfops

Seems fine. Do we no longer allow you to specify the project for the wasm and just require you point directly to the wasm binary?

I'm not 100% sure what you're asking so I hope this is clear: we never allowed users to specify both. Previously, --project-path could take either a directory or a wasm path. Then we added --wasm-file (now --bin-path) to make the behavior clearer, but we still quietly supported taking a wasm file via --project-path. After this PR, you use --project-path to provide a directory, and --bin-path to provide a wasm file (and you still can't provide both at once).

Nov 09 '24 03:11 bfops