-
Notifications
You must be signed in to change notification settings - Fork 743
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
Add = as Operator in Puppet lexer #980
Add = as Operator in Puppet lexer #980
Conversation
590e7f7
to
93893e2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR @alexharv074. Couple of comments.
The = sign had been missed apparently as a valid Puppet operator. Also adds tests. Fixes rouge-ruby#979.
93893e2
to
f0f5488
Compare
@dblessing , I refactored to avoid the confusing syntax as you suggested. Meanwhile, I left the Rspec tests in. I think they assist any future maintainers to get their heads around why a 2013-era syntax highlighter actually works on the latest version of Puppet? |
FWIW Rouge is constantly updated and lexers are added, updated, etc. as needed. When Rouge was created has no bearing one whether it does or doesn't support the latest version of some language. |
I'd generally prefer adding the example to |
Based on discussion on the PR, it is agreed to add sample code in spec/visual/samples/puppet and not have the Rspec tests that I added.
@dblessing @jneen for what it's worth, I found it much easier to analyse the behaviour of the lexers using the Rspec framework than I did using the debug output from |
@dblessing not sure if you're waiting on me here, but I can't find any way from my end to move this Issue out of "Changes requested" state. Let me know if there's anything else I am supposed to to? |
Any chance this could be merged now @dblessing ? |
@dblessing Looks like this was merged over 6 months ago but still my GitHub/Jekyll blog doesn't have the fix. Any idea why that might be? |
Make sure to update dependencies. Looks like this was released in Rouge
3.3.0.
Alex Harvey <[email protected]> schrieb am Mo. 25. März 2019 um
01:58:
… @dblessing <https://github.com/dblessing> Looks like this was merged over
6 months ago but still my GitHub/Jekyll blog doesn't have the fix. Any idea
why that might be?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#980 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ACSKlNqLdl6XcOqGo5SXEIrg4biPj3szks5vaHOOgaJpZM4WYqbe>
.
|
Yeah, I just specify latest jekyll on my side and the rest happens magically on the GitHub side. Ok, thanks for merging and releasing anyway! I'll investigate. |
The = sign had been missed apparently as a valid Puppet operator.
Fixes #979.