-
-
Notifications
You must be signed in to change notification settings - Fork 904
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
Deprecate positional hash arguments in the API #3200
Milestone
Comments
flavorjones
added a commit
that referenced
this issue
Jun 6, 2024
flavorjones
added a commit
that referenced
this issue
Jun 11, 2024
flavorjones
added a commit
that referenced
this issue
Jun 11, 2024
flavorjones
added a commit
that referenced
this issue
Jun 22, 2024
…ext (#3246) **What problem is this PR intended to solve?** Coming from the discussion at #3203, I wanted to improve the fragment parsing API - as discussed in #2646, parse in no-quirks mode if a context element name is provided (not a context `Node`, just the name) - allow passing `:context` kwarg to `DocumentFragment.new` and `.parse` - deprecate the positional options hash to `.parse` per notes at #3200 **Have you included adequate test coverage?** Included additional coverage for the API changes **Does this change affect the behavior of either the C or the Java implementations?** HTML5 is only in CRuby.
Closing this, related work at #3323 mostly addressed this in a backwards-compatible way. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently we've still got a few methods that use the pre-Ruby-3.0 convention of using a positional hash argument to pass options.
For example:
I'd like to start planning to deprecate these positional hashes in favor of true keyword arguments.
Note that we can't simply move to keyword arguments, since calls that use explicit hashes would stop working:
So we'll need to do an intermediate step that looks something like:
The text was updated successfully, but these errors were encountered: