Provide ability to disable prettify code highlighting #64
Conversation
| @@ -65,5 +65,8 @@ abstract class StyledVerbatimSerializer extends VerbatimSerializer { | |||
| */ | |||
| object PrettifyVerbatimSerializer extends StyledVerbatimSerializer { | |||
| override def printPreAttributes(printer: Printer): Unit = printClass(printer, "prettyprint") | |||
| override def printCodeAttributes(printer: Printer, nodeType: String): Unit = printClass(printer, s"language-$nodeType") | |||
| override def printCodeAttributes(printer: Printer, nodeType: String): Unit = nodeType match { | |||
| case "nocode" => printClass(printer, s"nocode") | |||
There was a problem hiding this comment.
Prettify uses nocode, I am open to suggestions for a better name.
There was a problem hiding this comment.
How about:
```text
foo
```
There was a problem hiding this comment.
Prettify will still try to highlight it. nocode is the only way to turn off this behaviour.
There was a problem hiding this comment.
Can we pass "nocode" to Prettify when the user types in ```text in addition to nocode?
There was a problem hiding this comment.
Example:
Yes, I can update to pass nocode when type is text (in addition to nocode)
jonas
force-pushed
the
nocode
branch
2 times, most recently
from
ddcb30b
to
5de755c
Compare
|
Updated to both map The alternative would be to always add the |
Either using:
```text
...
```
or for snippets:
@@ snip [apache.log](apache.log) { type=text }
|
Rebased and added notes entry |
|
This at least is where we can mirror and match GHM, so we should pick On Mon, 21 Nov 2016, 20:12 Jonas Fonseca, notifications@github.com wrote:
|
|
@dwijnand I'm guessing that Kramdown / Redcarpet or whatever that implements GFM uses https://help.github.com/articles/creating-and-highlighting-code-blocks/ |
|
Linguist I believe is the tool to categorise languages and I assumed it had On Mon, 21 Nov 2016, 21:54 eugene yokota, notifications@github.com wrote:
|
|
In addition to the per-snippet solution proposed here I think it'd be great if paradox also offered a way to completely disable the existing strong coupling with google-code-prettify. In my project for example we use IMHO paradox should offer an SBT setting that allows users to completely switch off any generation-time highlighting support. |
Either using:
or for snippets:
As discussed in lightbend/ssl-config#51 Paradox will eagerly highlight anything inside fenched code block. This PR provides an escape hatch for this behaviour.