Wrong manifest.toml linting result

Vega Open Beta Bug Reports
1

:warning: Before you continue

Before submitting a bug report, please review our troubleshooting documentation at Troubleshoot Issues | Vega Troubleshooting

If you still want to file a bug report, please make sure to fill in all the details below and provide the necessary information.

NOTE: PLEASE ONLY REPORT A SINGLE BUG USING THIS TEMPLATE.
If you’re experiencing multiple issues, please file a separate report for each.

:backhand_index_pointing_right: Bug Description

1. Summary

The Kepler ESLint plugin returns a wrong error message for manifest.toml linting.

Bug Severity

  • Impacts operation of app
  • Blocks current development
  • Improvement suggestion
  • Issue with documentation (If selected, please share the doc link and describe the issue)
  • Other

2. Steps to Reproduce

...
[components]
[[components.interactive]]
id = "de.prosiebensat1digital.seventv.main"
runtime-module = "/com.amazon.kepler.keplerscript.runtime.loader_2@IKeplerScript_2_0"
categories = ["com.amazon.category.main", "com.amazon.category.kepler.media", "com.amazon.category.kva"]
launch-type = "singleton"
...

3. Observed Behavior

image
image989×104 17.6 KB

4. Expected Behavior

The plugin should not complain about com.amazon.category.kva, as it’s mentioned often in the documentation (e.g., for Content Personalization, see @amazon-devices/kepler-content-personalization | Vega API )

3

Hi @Sebastian_Mader,

Thanks for reporting this. You’re correct — com.amazon.category.kva is a valid manifest category. It’s documented in the @amazon-devices/kepler-content-personalization | Vega API as the required category for interactive components that integrate with Vega’s media/content personalization features.

Our team is investigating this linting issue and will provide an update as soon as we have more information.

Thanks for helping us improve the Vega platform.

Warm regards,
Aishwarya