Open gabestein opened 3 weeks ago
@allisonking Do you think one endpoint should handle all of this? Or one endpoint per operation, kind of like @tefkah has each relationship-related function broken out?
Since we get an editor state from the the editor rather than a diff, I think ideally everything is one upsert, otherwise we'd have to track "this pubfield was removed" and then call the remove endpoint. but I also imagine doing everything in one upsert might be more difficult?
An open question: should we do this RESTfully, or is this complicated enough that we want an RPC-style structure
Although now that I'm looking at feat: add functions to interact with relationships more, there's a test specifically to not allow updating related pub relations via the current updatePub
function. I think this means the editor can update its own local pub, and then maybe call updatePub
on each of its related pubs?
Motivation
Requirements
Acceptance Criteria
Extra work