Actions
Bug #22009
closed
Invalid routes with NIL as a route param are selected
Status:
Closed
Priority:
Normal
Assignee:
Category:
Hammer core
Target version:
Difficulty:
Triaged:
Pull request:
Team Backlog:
Description
When API method has multiple routes the one with most route parameters is picked by api bindings. While all the parameters have to be defined we do not check for NIL values.
With NILs now allowed as a valid CLI param values it is happening that selected routes are invalid when any of the route params is NIL
Updated by Martin Bacovsky over 6 years ago
- Related to Bug #17252: Unable to set empty parameter via hammer added
Updated by Martin Bacovsky over 6 years ago
- Subject changed from Routes with NIL as a route param are selected to Invalid routes with NIL as a route param are selected
Updated by Martin Bacovsky about 6 years ago
- Status changed from Assigned to Closed
- translation missing: en.field_release set to 290
- Pull request https://github.com/Apipie/apipie-bindings/pull/70 added
Actions