Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • With best option, would a POST to create another user just omit the id? If so, is the risk of accidental omission of id(e.g. due to bug) resulting in creating new users rather than updating the existing one acceptable (I think so, but just wondering)? Commented Jun 4 at 9:56
  • it branches off into another topic ie. "should the object have an id before its persisted?" I think the general agreement is that it should, and so you use guids and have the client set the id, which means you can always include it. If you let the sever create the id, then sure, you can leave it null and return it, or have a CreateObjectRequest object with different properties or whatever Commented Jun 4 at 10:25
  • I think i would separate the create and update endpoints in either case as I would expect different business logic to be applied Commented Jun 4 at 10:27