Closed
Bug 909592
Opened 11 years ago
Closed 11 years ago
Collections API PATCH should accept locale object for localisable text fields
Categories
(Marketplace Graveyard :: API, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: basta, Unassigned)
Details
PATCHing a collection with the following request body:
{"description":{"en-US":"lol","bg":"bgtest","ca":"catest"}}
sets the "en-US" text to:
{"en-US":"lol","bg":"bgtest","ca":"catest"}
I.e.: the JSON object is stringified by the API and stored as the default locale, rather than being parsed and updated into the db.
|
||
Updated•11 years ago
|
Blocks: mkt-publishtool-api
|
|
||
Updated•11 years ago
|
No longer blocks: mkt-publishtool-api
Summary: Collections API PATCH should accept locale object for localizable text fields → Collections API PATCH should accept locale object for localisable text fields
|
||
Comment 1•11 years ago
|
||
Weird. Were you using application/json or something else ?
|
Reporter | |
Comment 2•11 years ago
|
||
Very strange. I can't reproduce this anymore from my home computer. I have no idea why I was seeing that. Maybe I'm not doing enough cache rewriting.
Anyway, if I see it again, I'll take a screenshot to prove I'm not insane and reopen the bug.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•