Bug #15420
full_results parameter is improperly defined in the API documentation
Team Backlog:
Fixed in Releases:
Found in Releases:
Description
The discrepancy exists in spelling 'full_results' versus 'full_result'. This change will change the API.
Related issues
Associated revisions
History
#1
Updated by The Foreman Bot about 3 years ago
Updated by - Status changed from New to Ready For Testing
- Pull request https://github.com/Katello/katello/pull/6126 added
#2
Updated by Anonymous about 3 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset katello|49469e2e05d1036351fa1caee2d607b851442dfa.
#3
Updated by Justin Sherrill about 3 years ago
Updated by - Legacy Backlogs Release (now unused) set to 162
#4
Updated by Andrew Kofink about 3 years ago
Updated by - Related to Bug #15443: Use fully qualified object ::Foreman in #15420 added
Fixes #15420 - Adjust full_results param (#6126)
While the API advertised a parameter named :full_results, our code was
expecting the param to be named :full_result. This change adds tests to
ensure the :full_results parameter can be used and is actually effective
in our system.
In addition, this changes the API parameter documented from
:full_results to :full_result
Furthermore, this parameter was failing to cast from a JSON string to a
boolean such that 'false', 'true', 0, or 1 would return a true value.
This introduces a proper cast using `Foreman::Cast.to_bool`.