Actions
Bug #22753
closedSome API parameters are wrongly documented as enum types
Description
There are several params in the apidoc that are wrongly documented as enum types. Authors most likely intended to validate the parameter for multiple allowed values, but apipie interprets the array syntax as enum.
E.g.:
param :value, LookupKey::KEY_TYPES # -> [ string, boolean, integer, real, array, hash, yaml, json ]
As a result hammer validates such options and raises an exception if ti contains values other than enumerated, which makes the commands unusable.
Updated by The Foreman Bot over 6 years ago
- Status changed from New to Ready For Testing
- Assignee set to Tomáš Strachota
- Pull request https://github.com/theforeman/foreman/pull/5286 added
Updated by Tomáš Strachota over 6 years ago
- Related to Bug #22751: Adding override values doesn't work with 1.17 added
Updated by Tomáš Strachota over 6 years ago
- Related to Bug #17087: Updating default_value of a hash/array smart class parameter with a non string value should return an error message added
Updated by Tomáš Strachota over 6 years ago
- Related to Bug #22754: Content view filter rule name param is wrongly documented as enum added
Updated by Anonymous over 6 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset cb591e34f4e1f462b826a5f391bed20ceb192da3.
Updated by Ivan Necas over 6 years ago
- Translation missing: en.field_release set to 330
Actions