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

Nokogiri::XML::Schema.read_memory() support keyword arguments #3333

Merged
merged 4 commits into from
Dec 6, 2024

Conversation

openbl
Copy link
Contributor

@openbl openbl commented Nov 14, 2024

What problem is this PR intended to solve?

Related to #3323, introducing keyword argument support in Nokogiri::XML::Schema.read_memory() and argument forwarding in Nokogiri::XML::Schema{,.new}().

Have you included adequate test coverage?

Some minor test coverage mimicking the existing permutations of options.

Does this change affect the behavior of either the C or the Java implementations?

No

@flavorjones flavorjones added the event/hackday2024 RubyConf 2024 Hack Day label Nov 15, 2024
@flavorjones flavorjones added this to the v1.17.0 milestone Nov 29, 2024
@flavorjones flavorjones self-assigned this Nov 29, 2024
@flavorjones
Copy link
Member

Thanks for your patience. The last couple of weeks have been really busy, but I'm hoping to review and merge this in the next week or so!

flavorjones and others added 3 commits December 6, 2024 14:13
and RelaxNG.read_memory is now forwarding to .new

Also increase depth of test coverage for constructors taking both
string and IO arguments
- document Schema.new as the primary constructor and
  Schema.read_memory is now forwarding to .new
- correct the Schema.read_memory documentation which incorrectly said
  that IO was not supported. Also updated the tests to cover that input
  type.
- add example for Schema.from_document
@flavorjones flavorjones force-pushed the xml-schema-arg-forwarding branch from 1e2632e to 23735e9 Compare December 6, 2024 19:29
@flavorjones
Copy link
Member

Rebased and tidied docs in Schema and RelaxNG (because they're so similar and I wanted them to be documented similarly)

@flavorjones flavorjones enabled auto-merge December 6, 2024 19:32
@flavorjones flavorjones disabled auto-merge December 6, 2024 21:09
@flavorjones flavorjones merged commit 0fffe34 into sparklemotion:main Dec 6, 2024
131 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
event/hackday2024 RubyConf 2024 Hack Day
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants