-
Notifications
You must be signed in to change notification settings - Fork 1
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
IE-517 Ruby 3.0.6 Compatibility #8
Conversation
Starting in 2013, gem-ified standard library gems were only made available through Bundler if the gem was specified in the Gemfile, see: sferik/multi_xml#42 As a result we started to get the error: "No XML parser detected. If you're using Rubinius and Bundler, try adding an XML parser to your Gemfile (e.g. libxml-ruby, nokogiri, or rubysl-rexml). For more information, see sferik/multi_xml#42." To fix this issue we need to specify an xml parser in our Gemfile. We're not going to be doing that much work within an auth Gem, so performance of the xml parser doesn't matter that much. But we picked libxml for performance anyways. (https://medium.com/neuronio/generating-xml-in-ruby-builder-vs-nokogiri-vs-libxml-vs-ox-757ce2d8f83c)
…th gem maintenance
@@ -1,5 +1,5 @@ | |||
module OmniAuth | |||
module Concur | |||
VERSION = "0.0.1" | |||
VERSION = "0.0.2" |
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.
This one is for you @wilkinsondesouza
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.
I appreciate that my rambling is being remembered 😄
@@ -1,5 +1,5 @@ | |||
module OmniAuth | |||
module Concur | |||
VERSION = "0.0.1" | |||
VERSION = "0.0.2" |
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.
I appreciate that my rambling is being remembered 😄
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.
LGTM. Your documentation / commit messages made this super easy to follow & understand why each change is happening. This devcontainer approach seems really interesting!
In order to make Ruby 3 compatible we had to:
For CI and maintenance we:
https://kantata.atlassian.net/browse/IE-517