Migration guide
Every breaking release has its own section below, newest first. If you are crossing several releases at once, work from the bottom of the page upwards.
Upgrading to v0.11.0 (from v0.10.x)
Upgrading to v0.10.0 (from v0.9.x)
Upgrading to v0.9.0 (from v0.8.x)
Upgrading to v0.8.0 (from v0.7.x)
The npm package no longer translates errors and no longer depends on @dynamicforms/translatable. It converts an error body into an ErrorDescription, and the application translates it by its code with the function it uses for its vue-forms errors. The response bodies are unchanged.
- ts
// before translateStrings((key) => myTranslations[key]); const message = translateApiError(body); // after const message = errorText(toErrorDescription(body));errorTextis the application's function described in vue-forms: Error messages and translation. It looks the code up in the application's translations, substitutesparamsand falls back todetail. Add the codes listed in Error codes to the translations; the placeholder names are the same.
Upgrading to v0.6.0 (from v0.5.7)
Nothing about a response body changes unless you opt in. There is no checklist for this release - see Error codes for what changed and how to opt into it.
NotFoundError moves from fastapi_viewsets.response_classes to fastapi_viewsets.exceptions:
# before
from fastapi_viewsets.response_classes import NotFoundError
# after
from fastapi_viewsets.exceptions import NotFoundError