There should be a CLI tool that validates manifest.toml, without requiring VSCode—something not every team may use (nor will continuous integration platforms).
This could be a separate kepler command, or just an automatic part of build.
Such a tool would make issues like this one easier to address before appstore submission.
Hi @mikey,
Thank you for this feature request! It turns out there’s already a CLI tool available that should address your need.
You can use the Vega Package Tool (vpt) to validate your manifest without VSCode:
vpt validate <vpkg or manifest.toml path>
This works with either your manifest.toml file directly or a packaged .vpkg file. The command checks your manifest against AppStore requirements and provides detailed, actionable error messages.
For more details, see the VPT Documentation.
If you run into any issues or if this doesn’t fully meet your needs, please let us know. Your feedback about discoverability is valuable and helps us improve our documentation.
Thanks for helping us improve the Vega platform.
Warm regards,
Aishwarya
Ah, that should work well, thank you!
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.