Timeline for Comments in user timeline are returning Markdown
Current License: CC BY-SA 2.5
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 20, 2011 at 22:36 | comment | added | Jonathan. | @Kevin, but why have one route return markdown and the others HTML, that's inconsistant, and you've just said that using markdown renderer is overkill, and that another request should be made, something that has been previously said should be kept to a minimum. | |
| Feb 20, 2011 at 21:47 | comment | added | Kevin Montrose |
@Jilouc - the simplest workaround is to query /comments/{id} for the html equivalent, and is the only one I've seen in practice. Pulling in a markdown renderer (even our OSS one) is probably overkill.
|
|
| Feb 20, 2011 at 21:46 | comment | added | Kevin Montrose |
@Jonathan - this is not a comment (comments are returned by /comments, /questions?comments=true, and so on), it is referring to a comment. The referred to bug did, originally, return html and when it switched to markdown that was a bug. This method has always returned markdown.
|
|
| Feb 20, 2011 at 21:46 | comment | added | Jilouc |
@Jonathan That was just a guess. I don't know how the API works internally so when Kevin says it's dangerous to fix it for the moment, I believe him. I'm going to use comments/{id} with vectorized comment ids to get the HTML version of timeline comments.
|
|
| Feb 20, 2011 at 21:26 | comment | added | Jonathan. | @Jilouc considering this seems to be the only route which returns markdown over HTML, and previously it was said this was a bug that has been fixed, it's pretty safe to assume that apps have not gone to the trouble of implementing markdown->HTML for this one occasion? | |
| Feb 20, 2011 at 21:17 | vote | accept | Jilouc | ||
| Feb 20, 2011 at 21:16 | comment | added | Jilouc | @Jonathan I don't know but if this is an old bug, fixing it may break existing apps that have worked around it. This is far from perfect, but I'll find a workaround too. | |
| Feb 20, 2011 at 20:46 | comment | added | Jonathan. | @Kevin you seriously expect apps to convert the markdown in HTML, in order to display it in a user friendly way. I'd love to know how the backend of the API works; if changing this is considered dangerous, it seems the API is held together with bits of tape, and a few kicks. | |
| Feb 20, 2011 at 19:51 | history | answered | Kevin Montrose | CC BY-SA 2.5 |