fix: json >= 3.0 is causing a wrong number of arguments - #427
Open
dominikschidlowskidmde wants to merge 1 commit into
Open
dominikschidlowskidmde wants to merge 1 commit into
dominikschidlowskidmde wants to merge 1 commit into
Conversation
dominikschidlowskidmde
force-pushed
the
fix/json-3-parse-arity
branch
from
September 14, 2026 13:03
78a593e to
62d04cc
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #426.
jsonv3.0 changedJSON.parse's signature to keyword-onlyarguments and removed the
create_additionsoption entirely, soClient#successand
Client#errorraiseArgumentError: wrong number of arguments (given 2, expected 1)on any successful or JSON-error response oncejson3.x isresolved.
Changes
JSON.parse(response.body, JSON_PARSE_OPTIONS)→JSON.parse(response.body, **JSON_PARSE_OPTIONS)at the two call sites in
lib/vault/client.rb.create_additions: falsefromJSON_PARSE_OPTIONS—json3.xremoved the option outright. Not a behavior change:
create_additionshasdefaulted to
falseforJSON.parse(as opposed toJSON.load) since atleast v1.8.6.
spec/unit/client_spec.rbexercising#success/#erroragainst a real JSON response body — the existing suite passed unchanged
under
json3.0.2 even without this fix, since nothing drove a JSON-typedresponse through those methods.