Closed feliperaul closed 2 years ago
Hi, thanks for kind words, I'm glad you like this library and thanks for pointing this issue. I will investigate and probably change the default behaviour so you have to set XML adapter explicitly.
@feliperaul I just released a new version v0.5.0 that drops the requirement on REXML. I will close the issue. If you still have problems please reopen it or create a new one.
Changelog: https://www.shalerb.org/releases.html
@kgiszczak Thank you!
Hi there! First of all, what a nice gem you've given us here. Amazed by how elegant it's API turned out to be. Excited to use it in a new API integration.
Also, 300+ stars, all these features, and no issues? Not even closed ones? What kind of sorcery is that? 😃
Anyways, I'll be the first. I was facing this exception when trying to use it in a Rails project with Ruby 3.1:
According to this blog post, rexml is now a bundled gem, so I had to add it manually in my gemfile as well, which fixed it.
In our case, since performance isn't a huge concern, I'd like to avoid the
rexml
dependency and use Nokogiri that we already use. Tried changing the adapter in an initiailzer, as per the gem's README instructions, but it raises the exception before reaching the initializer.Maybe the requirement of
rexml
could be relaxed, or else instructions for addingrexml
in the Gemfile could be added in the readme.