You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're closing in on the v0.3 release of the OPS CLI. This will be a very significant release, including two major improvements to facilitate simulation setup: the wizard command, and the compile command. I'd like to keep a task list here of things that still need to be done prior to the v0.3 release:
Finish JSON schema types for existing compile plugins (#67)
Docs for compile and wizard command in OPS core docs (PR coming soon)
Restructure OPS CLI docs to include info on writing compile and wizard plugins
Feedback from beta testers
@sroet : Anything else you see as necessary for this? I'll be asking you (and a few others) to test-drive the compile and wizard commands once I have preliminary docs up (although the wizard probably doesn't even need docs). Mainly, I'm hoping you can catch any bugs (bad user input should not crash the wizard, and should give understandable error messages in compile) and identify priorities for further developments.
The text was updated successfully, but these errors were encountered:
We're closing in on the v0.3 release of the OPS CLI. This will be a very significant release, including two major improvements to facilitate simulation setup: the
wizard
command, and thecompile
command. I'd like to keep a task list here of things that still need to be done prior to the v0.3 release:compile
plugins (#67)compile
andwizard
command in OPS core docs (PR coming soon)compile
andwizard
plugins@sroet : Anything else you see as necessary for this? I'll be asking you (and a few others) to test-drive the
compile
andwizard
commands once I have preliminary docs up (although thewizard
probably doesn't even need docs). Mainly, I'm hoping you can catch any bugs (bad user input should not crash the wizard, and should give understandable error messages incompile
) and identify priorities for further developments.The text was updated successfully, but these errors were encountered: