Skip to content

Latest commit

 

History

History
19 lines (15 loc) · 1.24 KB

migratingFromAddonFiles.md

File metadata and controls

19 lines (15 loc) · 1.24 KB
Raw

Migrating from addonFiles to addon-datastore

Add-ons which used to be registered in the addonFiles repository are made available through a legacy endpoint. The legacy community add-ons website is dependent on this endpoint. Other consumers may also be dependent on this endpoint.

When migrating to the new add-on datastore, publishers may wish to update their add-on ID, instead of using the one registered in addonFiles.

Updating legacy add-on IDs

Updating casing to lowerCamelCasing

The legacy endpoint is case-insensitive, meaning authors can easily update the casing in the new add-on datastore. Just open a pull request changing the casing of the add-on ID folder name, and the add-on ID for all the submission files in the folder.

Renaming add-on ID

  1. Submit the new add-on to this repository.
  2. Update the community add-ons website to use the new add-on ID. Ask for help in nvda-addon's mailing list.
  3. Consider deleting the legacy add-on submission in this repository.