New version broke XML::Document.io about libxml-ruby HOT 8 CLOSED

Yes, that is correct, and a breaking change (thus the 5.0.0 version). Passing options was switched to use keyword parameters instead of the old style of passing hashes (see the release notes). You'll have to update your code. Sorry for the breakage, but this seemed like the right time to do the API change to go along with the deprecation of global settings in limbxml2 2.12.

from libxml-ruby.

The note is in the changelog. See https://github.com/xml4r/libxml-ruby/blob/master/HISTORY

FYI #211 is a definitely a bug and fixed.

from libxml-ruby.

Sorry, I couldn't find a place in the documentation where it says that we need to pass keyword params. Here? (link from the github page).

Well, this is how the the method io is defined:

module LibXML
  module XML
    class Document
     #...
     def self.io(value, options = {})
         Parser.io(value, options).parse
     end
     #...
  end
end

which invokes this method here

module LibXML
  module XML
    class Parser
      #...
      def self.io(io, base_uri: nil, encoding: nil, options: nil)
        context = XML::Parser::Context.io(io)
        context.base_uri = base_uri if base_uri
        context.encoding = encoding if encoding
        context.options = options if options
        self.new(context)
      end
      #...
  end
end

So, self.io methods requires an IO object and an optional options.

Moreover, I call simply by

XML::Document.io(StringIO.new("<xml>Hello, world!</xml>"))

from libxml-ruby.

Seems like I opened a duplicate but similar query here -> #211

It looks like the library has a bug from what I understand.

from libxml-ruby.

@vseguin But @cfis thinks differently, "breaking changes" and closed right away.

from libxml-ruby.

@fade2black it does seem that @cfis fixed it now, just waiting for a new update to be released 🙌 Thanks for being super-reactive here.

from libxml-ruby.

@cfis You wrote to me

Yes, that is correct, and a breaking change (thus the 5.0.0 version). Passing options was switched to use keyword parameters instead of the old style of passing hashes (see the release notes). You'll have to update your code. Sorry for the breakage, but this seemed like the right time to do the API change to go along with the deprecation of global settings in limbxml2 2.12.

What does that mean? I guess it is YOU should fix your buggy code (if it is a bug) or add corresponding docs, not me to update my APIs.

from libxml-ruby.

@cfis FYI Unlike you I do know very well semver and CO and can tell apart bug from a breaking changes.
You first screw up, next blame me that I need to "update my APIs" instead of having close look at your bug, and then make a sneak fix? This is childish, irrespecutful, and unprofessional of you. I wonder how a "developer" like you maintains this gem. That explains why it lacks a proper documentation and does not have proper tests that catch such simple bugs.

from libxml-ruby.