Skip to content
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

Upgrade rouge to 2.0.7 #10

Merged
merged 4 commits into from
Apr 6, 2017
Merged

Conversation

hibariya
Copy link
Collaborator

@hibariya hibariya commented Apr 6, 2017

Hello. Thank you for the nice integration gem!

Since there are new lexers and fixes which were added after rouge-0.8, I'd love to use html-pipeline-rouge_filter with latest rouge (2.0.7).

The API of rouge has been changed since 2.0.0. Although I'm not sure how to deal with these new formatters via this filter, it seems possible to upgrade rouge without making API changes by using Rouge::Formatters::HTMLLegacy for now. This Pull Request does it.

What do you think? Let me know your opinion.

@@ -95,6 +95,6 @@ def test_replacing_br

doc = filter.call
assert_equal "<pre class=\"highlight highlight-ruby\"><code>"\
"<span class=\"n\">hello</span>\n<span class=\"n\">world</span></code></pre>\n", doc.to_html
"<span class=\"n\">hello</span>\n<span class=\"n\">world</span></code></pre>", doc.to_html
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Line is too long. [107/80]

@JuanitoFatas
Copy link
Owner

JuanitoFatas commented Apr 6, 2017

The API of rouge has been changed since 2.0.0. Although I'm not sure how to deal with these new formatters via this filter, it seems possible to upgrade rouge without making API changes by using Rouge::Formatters::HTMLLegacy for now. This Pull Request does it.

Good for now 👍

Oh wow, thanks so much for the upadtes, looks like CI-san is not happy 😂 Would you take a look into that 🙏

@hibariya
Copy link
Collaborator Author

hibariya commented Apr 6, 2017

Oh wow, thanks so much for the upadtes, looks like CI-san is not happy Would you take a look into that

Sure. I'll investigate that 🙋‍♀️

* activesupport-5.0.0 or later don't support ruby < 2.1.0.
* Latest activesupport (5.0.2) doesn't support ruby < 2.2.2.
* nokogiri-1.7.0 or later don't support ruby < 2.1.0.
@hibariya
Copy link
Collaborator Author

hibariya commented Apr 6, 2017

There are some gems which don't support certain old runtime. I've made setting upper limit of these versions only if the runtime is not supported by latest gems (43096f3).

  • activesupport-5.0.0 or later don't support ruby < 2.1.0.
  • Latest activesupport (5.0.2) doesn't support ruby < 2.2.2.
  • nokogiri-1.7.0 or later don't support ruby < 2.1.0.

@JuanitoFatas JuanitoFatas merged commit 36be089 into JuanitoFatas:master Apr 6, 2017
@JuanitoFatas
Copy link
Owner

Thanks so much for the hard work!!!!! 👍 💯

Do you want to be a committer of this project? 👩🏻‍💻

@JuanitoFatas
Copy link
Owner

Shipped in v1.0.5!!! 🐑

@hibariya
Copy link
Collaborator Author

hibariya commented Apr 6, 2017

Thanks!!!!!

Do you want to be a committer of this project? 👩🏻‍💻

Yes I do 😸 It's an honor.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants