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
Proposing to support the query_string/queryParams/_query key (or similar) in the $params/$options array for specifying these parameters.
The name must also be quite unique to avoid conflict with any of Request body parameters, that we any of current JIRA API calls (according to docs) can use.
The text was updated successfully, but these errors were encountered:
Having some special key in the $data parameter of the Api::api method looks a bit weird, but adding yet another optional parameter to the Api::api method (it already has 6 parameters) looks like an even worse decision to me.
Some of the API calls support both request body parameters and query string parameters (e.g. https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-issue-worklogs/#api-rest-api-2-issue-issueidorkey-worklog-id-put ).
Proposing to support the
query_string
/queryParams
/_query
key (or similar) in the$params
/$options
array for specifying these parameters.The name must also be quite unique to avoid conflict with any of
Request body
parameters, that we any of current JIRA API calls (according to docs) can use.The text was updated successfully, but these errors were encountered: