We have made some improvements to the records updating logic in ticket:
3412
The previous includes some improvement to the records updating logic at frontend.
However, pure frontend effort won't be able to address all edging cases.
e.g. Because the current PUT /api/v0/registry/records/{recordId} only supports the replace behaviour, it requires API invoker always to include all record data (including access-control-aspect).
This might not always be feasible when you only want to update certain fields of the aspect without touching other fields.
Once this ticket:
3420
is done, we will be able to further improve the records updating logic to address all edging cases.
Changes should be properly test to make sure issue #3412 will not break again
We have made some improvements to the records updating logic in ticket:
3412
The previous includes some improvement to the records updating logic at frontend.
However, pure frontend effort won't be able to address all edging cases.
e.g. Because the current
PUT /api/v0/registry/records/{recordId}
only supports thereplace
behaviour, it requires API invoker always to include all record data (includingaccess-control-aspect
).This might not always be feasible when you only want to update certain fields of the aspect without touching other fields.
Once this ticket:
3420
is done, we will be able to further improve the records updating logic to address all edging cases.