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
Thanks for this plugin, works great for our team. Currently, I'm having an issue with an API not accepting an empty string value when a query parameter is sent. For example, foo="" results in a 500 with the reason being that "foo must be set to info, critical, or warning". I was wondering if adding an additional checkbox for a parameter to not be sent makes sense to do. At the moment, I'm not sure how this could be communicated to the user either.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
Thanks for this plugin, works great for our team. Currently, I'm having an issue with an API not accepting an empty string value when a query parameter is sent. For example, foo="" results in a 500 with the reason being that "foo must be set to info, critical, or warning". I was wondering if adding an additional checkbox for a parameter to not be sent makes sense to do. At the moment, I'm not sure how this could be communicated to the user either.
Beta Was this translation helpful? Give feedback.
All reactions