You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#870 updated NQ parameter handling to align with how Deliverator handled them (ie all are optional but you must specify at least one).
The initial Protagonist implementation was to make every parameter be a required parameter. We should introduce a slightly new syntax that allows parameters to be marked as required. The syntax is to use the same p* format but add a trailing ! if it is required (e.g. p1!).
E.g.
s1=p1 would fail if no args were passed (despite it being p1 only as we need at least 1 arg)
s1=p1! would have same affect as above
s1=p1&s2=p2 would allow it to be called with /one or /one/two
s1=p1!&s2=p2 would be the same as above
s1=p1&s2=p2! would allow it to be called with /one/two only, /one would result in an error as the 2nd parameter is required.
s1=p1!&s2=p2!&s3=p3 accepts /one/two, or /one/two/three
s1=p1!&s2=p2&s3=p3! isn't valid - should this throw an exception on Create/Update?
The text was updated successfully, but these errors were encountered:
#870 updated NQ parameter handling to align with how Deliverator handled them (ie all are optional but you must specify at least one).
The initial Protagonist implementation was to make every parameter be a required parameter. We should introduce a slightly new syntax that allows parameters to be marked as required. The syntax is to use the same
p*
format but add a trailing!
if it is required (e.g.p1!
).E.g.
s1=p1
would fail if no args were passed (despite it beingp1
only as we need at least 1 arg)s1=p1!
would have same affect as aboves1=p1&s2=p2
would allow it to be called with/one
or/one/two
s1=p1!&s2=p2
would be the same as aboves1=p1&s2=p2!
would allow it to be called with/one/two
only,/one
would result in an error as the 2nd parameter is required.s1=p1!&s2=p2!&s3=p3
accepts/one/two
, or/one/two/three
s1=p1!&s2=p2&s3=p3!
isn't valid - should this throw an exception on Create/Update?The text was updated successfully, but these errors were encountered: