`parse-backticks` doesn't work in Discussions
See original GitHub issueI’ve started this discussion https://github.com/tophf/mpiv/discussions/50
and the text in backticks is not rendered, not in the post title, in the listing,
even though the parse-backticks
feature is listed ok in Console ()
There’s no error in Console.
Using Refined GitHub 21.2.9 with Chrome 88/Firefox 85.
Screenshots
(in a fresh Chrome profile)
If I may help, checking https://github.com/sindresorhus/refined-github/blob/main/source/features/parse-backticks.tsx I see there’s no selector for Discussion pages/listings. I think these would be:
.js-issue-title
for discussion pagesa[data-hovercard-type="discussion"]
for discussion listings
Thank you
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:9 (9 by maintainers)
Top Results From Across the Web
`parse-backticks` doesn't work in Discussions · Issue #3975
I've started this discussion tophf/mpiv#50 and the text in backticks is not rendered, not in the post title, in the listing,
Read more >Escaping back-ticks works in comments, but not in answers?
I'm using the "triple back-tick" workaround from this other question to handle things now, but why is the markdown parsing different for comments...
Read more >The old ticks vs parentheses issue: confused
The main reason to prefer parentheses in my view is that parsing inside $() is consistent with parsing performed outside, which isn't the...
Read more >Formatting Guide
Just writing two backticks to open the inline code and a single backtick to begin the inline code doesn't work because it looks...
Read more >A problem with backtick code fences - Spec
While Python (single-line) strings are always delimited by a single " or ' character, in Markdown any number of backticks can be used...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
No that is still not good since it applies to every issue page.
Also I would rather wait for #4135 before doing this change.
Here it is: https://github.com/sindresorhus/refined-github/pull/3977 🙂