Actions
Architecture #26390
open
Architecture #26335: Port RestApiAccount api endpoint to zio-json
API Accounts model needs to be consistent accross backend and frontend
Status:
Pending technical review
Priority:
N/A
Assignee:
Category:
API
Target version:
Fix check:
To do
Regression:
No
Description
- On the backend : the
expirationPolicyhas a dependency with theexpirationDatefield, it is a common issue that makes it hard to track the dependency and lifecycle of expiration. It has already been modeled as single type on the frontend, but maybe there are other case like this one (generate token, depending on the ID field when creating an account ?) - On the frontend : several elements in the model have changed since the API has changed to be released publicly, they have been mostly kept as is for compatibility in parent issue, but need to be reviewed according to the data model (e.g.
statusfield, and we now use ISO8601 dates and we could be more informative on dates timezone)
Updated by
Actions