Timeline for API /answers/{id}/flags/add route has multiple bugs
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 23, 2016 at 18:04 | comment | added | user315433 | Too late for me to repro now, since the post is deleted. I wanted to double-check that the option_id was for indeed for NAA. I've been using API to cast NAA flags for a long time, and it works fine for me. The NAA option is indexed [2] in the list returned by /flags/options | |
| Nov 23, 2016 at 18:03 | comment | added | Cai | @Art you are right, I thought it was available IDs that changed per post not actual IDs | |
| Nov 23, 2016 at 17:39 | comment | added | ArtOfCode | @Cai option IDs change per post | |
| Nov 23, 2016 at 16:52 | comment | added | Cai |
option_id: 22992 is "other" which does require a comment
|
|
| Nov 23, 2016 at 16:51 | comment | added | ArtOfCode | @zaq that explains it. As for the first one, the option_id comes from a previous API request. | |
| Nov 23, 2016 at 16:47 | comment | added | user315433 | Preview:true means you are not creating a flag, so the second part is not a bug. About the first one, I don't have an idea, perhaps the option_id isn't stable and you should fetch it from the rails app? | |
| Nov 23, 2016 at 16:37 | history | asked | ArtOfCode | CC BY-SA 3.0 |