[Bugfix] Allow the "null" JSON string to be used as a parameter in Apipie spec examples (show_in_doc
)
#641
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.
Ensure that Extractor::Recorder always rewinds rack.input because it is always read
This allows the parameters of a rack request to be the
null
JSON string,"null"
, when running apipie-example-updating commands:There are times when
parse_data(...)
can returnnil
(specifically, when evaluatingJSON.parse("null")
, the response isnil
).The current error
This fixes the following types of specs:
When running these specs, Apipie will analyze the env:
So far nothing bad happens, but then, to actually read the specs,
action_dispatch/http/request
will try to read the params:The fix
Note that if you run the specs without apipie, you get the correct behavior. This fix restores that:
Other stuff
"null"
is a valid JSON string: