Vuforia's result codes table spells this result code ProjectHasNoApiAccess, with Api rather than API. vws-python-mock is changing to match the documented spelling in VWS-Python/vws-python-mock#3352, and vws-python is tracking the mapping change in VWS-Python/vws-python#3128.
vws-cli keys its error messages by exception class rather than by result code string:
https://github.com/VWS-Python/vws-cli/blob/main/src/vws_cli/_error_handling.py#L45
So no mapping change is needed here, but the CLI currently depends on vws-python mapping the result code at all: VWSError.from_result_code does a plain dict lookup, so an unmapped spelling raises KeyError and the CLI reports an unhandled traceback instead of the friendly message.
Acceptance criteria
- After
vws-python maps ProjectHasNoApiAccess, the CLI reports "Error: The request could not be completed because this database is not allowed to make API requests." for a response using that spelling. - The
vws-python version bound is raised to a release that maps the documented spelling.
Vuforia's result codes table spells this result code
ProjectHasNoApiAccess, withApirather thanAPI.vws-python-mockis changing to match the documented spelling in VWS-Python/vws-python-mock#3352, andvws-pythonis tracking the mapping change in VWS-Python/vws-python#3128.vws-clikeys its error messages by exception class rather than by result code string:https://github.com/VWS-Python/vws-cli/blob/main/src/vws_cli/_error_handling.py#L45
So no mapping change is needed here, but the CLI currently depends on
vws-pythonmapping the result code at all:VWSError.from_result_codedoes a plain dict lookup, so an unmapped spelling raisesKeyErrorand the CLI reports an unhandled traceback instead of the friendly message.Acceptance criteria
vws-pythonmapsProjectHasNoApiAccess, the CLI reports "Error: The request could not be completed because this database is not allowed to make API requests." for a response using that spelling.vws-pythonversion bound is raised to a release that maps the documented spelling.