-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
[Website] Bad syntax highlighting #4029
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
Comments
This is because we have some unquoted values starting with |
This PR was merged into the 2.3 branch. Discussion ---------- enclose YAML strings containing % with quotes | Q | A | ------------- | --- | Doc fix? | yes | New docs? | no | Applies to | all | Fixed tickets | #1886, #4029 Thanks @iamdto, did you spot some other occurences in the docs? Commits ------- c1c4bc8 remove "..." from XML element tags dbc02a2 quote YAML strings starting with % or @ characters
I guess with #4030 being merged now, this can be closed. |
At least, the documentation issues in this issue are now fixed. Thanks you, @iamdto for you help in catching and finding the problematic spots in the docs! @javiereguiluz can you please fix the blog post? |
@wouterj I don't know what we should fix in the blog post. The first YAML code block appears with the right colors (but unnumbered). Is that correct? |
@javiereguiluz this is what I'm seeing: It doesn't have the right colors (only background color) and it is unnumbered because the highlighter isn't executed. That's because it contains an "error" (it was an error in Yaml 1.0). You should update it like this: monolog:
handlers:
main:
type: stream
--- path: %kernel.logs_dir%/%kernel.environment%.log
+++ path: "%kernel.logs_dir%/%kernel.environment%.log"
level: debug
console:
type: console |
@wouterj thanks for the explanation :) @Tobion could you please edit this blog post that you published and enclose the value of the |
Cool I can edit this. This is new. I've updated it. |
👍 |
Thanks @Tobion ! |
It looks like syntax highlighting is broken on some code blocks. For example on the framework full default configuration. I've noticed this in some blog posts too (the first Monolog configuration block for example).
Not sure if it's a bug or a feature, though.
The text was updated successfully, but these errors were encountered: