Timeline for Comments have incorrect `can_flag` values for at least 2 different API routes
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 27, 2018 at 18:12 | comment | added | Brock Adams | @AVK, there is no mention of any date parameter in your original bug report, nor the comment. ... And it does not seem necessary to replicate this bug (as outlined in the answer, anyway). | |
| Aug 27, 2018 at 18:01 | comment | added | AVK |
IDK How SE is caching the calls but if i do not pass the parameter and if i make any number of subsequent calls, it always comes back as true. When i posted this question, i mentioned i tried after 30 mins. When i made the call after 30 mins, without the parameter, it comes back true. But if i pass the parameter todate with the value above, it comes back as false. You can see this in Stack10.
|
|
| Aug 27, 2018 at 17:32 | comment | added | Brock Adams | @AVK, I don't see how that last comment is related to your bug report here at all. | |
| Aug 27, 2018 at 12:53 | comment | added | AVK |
I forgot that i posted a question. the API Browser works fine. The issue is when i do a REST call, i need to include parameter todate and always post the current second like Math.Floor(DateTime.UtcNow.Subtract(new DateTime(1970, 1, 1)).TotalSeconds) and it always brings the current status. This also happens with Questions api call. If you do not pass todate, you will keep receiving same questions over and over. Again this is only in REST Side. from API Browser it works fine.
|
|
| Aug 26, 2018 at 21:41 | history | edited | Brock Adams | CC BY-SA 4.0 |
added 73 characters in body
|
| Aug 26, 2018 at 0:36 | history | answered | Brock Adams | CC BY-SA 4.0 |