For further actions, you may consider blocking this person and/or reporting abuse
For further actions, you may consider blocking this person and/or reporting abuse
Cat -
Andrew Smith -
Venkatesh bellale -
Jysan Aziz -
Once suspended, markadell will not be able to comment or publish posts until their suspension is removed.
Once unsuspended, markadell will be able to comment and publish posts again.
Once unpublished, all posts by markadell will become hidden and only accessible to themselves.
If markadell is not suspended, they can still re-publish their posts from their dashboard.
Once unpublished, this post will become invisible to the public and only accessible to Mark Adel.
They can still re-publish the post if they are not suspended.
Thanks for keeping DEV Community safe. Here is what you can do to flag markadell:
Unflagging markadell will restore default visibility to their posts.
Top comments (1)
I think of this in terms of the
PUTorPATCHmethod. When you usePUT, you provide some data and you say "please store this data at the location (uri) I've specified". For example:PUT /books/3will take the information about a particular book from the body of a request and store that information in/books/3. You can then retrieve that information withGET /books/3. It's part of the contract forPUTthat you can useGETin this way afterward.How does this apply to the "store" resource archetype? The main idea is that the client tells the server what uri to use for a given resource. As a counter-example, with
POST, you'd do something likePOST /books. This would take the information about a book from the body of the request and create a new book resource. However, the client has no control over how to retrieve that book - so this would be the "collection" archetype.Note: The difference between
PUTandPATCHis thatPUTrequires all of the data for a book (it will replace the book) whereasPATCHwill leave any existing data alone. For example, withPATCHyou can update just the title of a book, leaving out the other fields. If you did that withPUT, any other fields would be removed. In both cases, if the record does not exist at the specified uri, it will be created, and if it does exist, it will be either replaced (PUT) or updated (PATCH).