Rob, William and myself have touched base about this and we agreed to leave the schema as is on the Firefox side (and wontfix this issue) and instead aim to remove the workaround we are currently using on the addons-linter side by reworking the way we import the schema data into the addons-linter (e.g. by merging the multiple separated JSONSchema files into a single normalized JSONSchema file, where the enum wouldn't be empty because all the values added to the enum from the per-API JSONSchema files would be merged into the enum at addons-linter's "Firefox API schema import"-time)
Bug 1942814 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Rob, William and myself have touched base about this and we agreed to leave the schema as is on the Firefox side (and wontfix this issue) and instead aim to remove the workaround we are currently using on the addons-linter side by reworking the way we import the schema data into the addons-linter (e.g. by merging the multiple separated JSONSchema files into a single normalized JSONSchema file, tracked by https://github.com/mozilla/addons-linter/issues/4511, where the enum wouldn't be empty because all the values added to the enum from the per-API JSONSchema files would be merged into the enum at addons-linter's "Firefox API schema import"-time)