Hi there,
First of all, thank you for maintaining this excellent package. It has been great for our standardized API development.
I am writing to ask about the current roadmap regarding the Atomic Operations extension (JSON:API v1.1).
The Use Case:
I have a scenario where I need to create a parent resource and its related children in a single, transactional request (e.g., creating a CalendarEvent and its Speakers simultaneously).
Currently, to stick strictly to the spec, I have to make multiple requests, which introduces the risk of "orphaned" records if a subsequent request fails, or forces me to use non-standard approaches (like "side-posting" data within attributes) to achieve transactional integrity.
The Feature:
Ideally, I would like to use the atomic:operations extension to send a bulk payload using lid (Local IDs) to link resources that are being created in the same request, ensuring that either everything persists or nothing does.
Question:
Is there any plan or estimated timeline to implement support for Atomic Operations in the near future?
If not, do you have any recommended approach or workaround to handle this kind of transactional "bulk create" within the current architecture of the package?
Thanks!
Hi there,
First of all, thank you for maintaining this excellent package. It has been great for our standardized API development.
I am writing to ask about the current roadmap regarding the Atomic Operations extension (JSON:API v1.1).
The Use Case:
I have a scenario where I need to create a parent resource and its related children in a single, transactional request (e.g., creating a
CalendarEventand itsSpeakerssimultaneously).Currently, to stick strictly to the spec, I have to make multiple requests, which introduces the risk of "orphaned" records if a subsequent request fails, or forces me to use non-standard approaches (like "side-posting" data within
attributes) to achieve transactional integrity.The Feature:
Ideally, I would like to use the
atomic:operationsextension to send a bulk payload usinglid(Local IDs) to link resources that are being created in the same request, ensuring that either everything persists or nothing does.Question:
Is there any plan or estimated timeline to implement support for Atomic Operations in the near future?
If not, do you have any recommended approach or workaround to handle this kind of transactional "bulk create" within the current architecture of the package?
Thanks!