Add-on API changes have been merged, planned for inclusion in the 2023.2 release:
"Update Add-on Manifest spec descriptions (#14754)"Suggested conventions have been added to the add-on manifest specification.
These are optional for NVDA compatibility, but are encouraged or required for submitting to the add-on store.
The new suggested conventions are:
- Using lowerCamelCase for the name field.
- Using <major>.<minor>.<patch> format for the version field (required for add-on datastore).
- Using https:// as the schema for the url field (required for add-on datastore).
If these suggestions cause difficulties for the ongoing development of an add-on you maintain, please let NVDA developers know by replying directly to emails, or via GitHub.
There are plans to move to a unified JSON schema, merging the manifest and add-on datastore JSON schema in 2024.1.
This will change how the add-on manifest is structured, and replacing the need for a separate schema to submit to the add-on store.