-
Notifications
You must be signed in to change notification settings - Fork 189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue view doesn't handle GitHub Markdown checkboxes properly [reopened] #80
Comments
Github checkboxes are not part of Markdown, they've got their own logic |
I'm going to have a go at this, see what I can do :) |
This is the start of the process of fixing bountysource#80 Signed-off-by: Cruz Julian Bishop <[email protected]>
Some more work is needed to render completed items. References bountysource#80 Signed-off-by: Cruz Julian Bishop <[email protected]>
This is the last image-related change. Ref: bountysource#80 Signed-off-by: Cruz Julian Bishop <[email protected]>
I've submitted a pull request for the front end work, and added a new issue for the back end work. If the back end work is done according to the proposal, no more front end work will need to be done - Otherwise, I'd be happy to modify the front end again. |
Damn it I'll reformat back to Arch tonight and have a look over the next few days, see what's going on. Here I was thinking I was safe :P Any estimates on how long ago it stopped working? A few days? Today? |
I'm sure it's something we did and didn't notice until recently. At some point we changed how issue bodies were rendering. Possibly 2-3 months ago? @corytheboyd any idea? |
I believe we started storing markdown source instead of the rendered HTML. |
Checkboxes on Bountysource currently look like:

and they should look like:

URL to example above:
https://www.bountysource.com/issues/538209
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: