Project

General

Profile

Bug #22009

Invalid routes with NIL as a route param are selected

Added by Martin Bacovsky over 2 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Normal
Category:
Hammer core
Difficulty:
Triaged:
Bugzilla link:
Team Backlog:
Fixed in Releases:
Found in Releases:
In Kanboard:

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


Related issues

Related to Hammer CLI - Bug #17252: Unable to set empty parameter via hammerClosed2016-11-07

History

#1 Updated by Martin Bacovsky over 2 years ago

  • Related to Bug #17252: Unable to set empty parameter via hammer added

#2 Updated by Martin Bacovsky over 2 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

#3 Updated by Martin Bacovsky over 2 years ago

  • Legacy Backlogs Release (now unused) set to 290
  • Status changed from Assigned to Closed
  • Pull request https://github.com/Apipie/apipie-bindings/pull/70 added

Also available in: Atom PDF