Skip to content

Change the handling of new Users in the UserRepository #3

@wimplash

Description

@wimplash

Either my understanding of REST semantics is slightly off or backbone.js is.

I currently have a PUT handler defined on the UserRepository at /resources/user/id/{id}. This assumes an empty body on the request and returns an "empty" (contains a system-assigned id and url) user representation in the response. This User is then filled out in the client and PUT back to the same /resource/user/id/{id} path.

Backbone, on the other hand, expects a fully-populated POST to the collection at /resources/user/ for creation and a PUT to the url for an updated User at /resources/user/id/{id}.

Change the create/update model for users in UserResource to match the semantics expected by Backbone.js.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions