Change HTTP status code from 200 to 201 on object creation#881
Change HTTP status code from 200 to 201 on object creation#881CalRL wants to merge 1 commit intosupabase:masterfrom
Conversation
A bit pedantic, however while I was making a small wrapper in rust i mistakenly matched for 201 status code, to me it's just intuitive for this to return 201
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review infoConfiguration used: Central YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Cache: Disabled due to Reviews > Disable Cache setting Disabled knowledge base sources:
📒 Files selected for processing (1)
📝 WalkthroughSummary by CodeRabbit
WalkthroughThe default HTTP status code for object creation responses has been updated. When Tip Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs). Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
A bit pedantic, however while I was making a small wrapper in rust i mistakenly matched for 201 status code, to me it's just intuitive for this to return 201
What kind of change does this PR introduce?
HTTP Status Code response change
What is the current behavior?
Currently on object creation, 200 is returned, http spec indicated that 201 should be used when a resource is created and or returned
What is the new behavior?
Returns 201 CREATED instead
Additional context
kindof a nothing burger pr but i was scratching my head for a second while making my rust wrapper, checking for 201 after uploading an image