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
When creating links with the API, omitting the description key entirely or passing { "description": null } produces a link with "description": null. However if I pass an empty string ({ "description": "" }) I get back a link with "description": "". AFAIK this doesn't affect the behavior of the link redirector, but it is annoying from an API perspective as it means I have to check if the description is empty instead of just checking if it's non-null.
Expected behavior:
Passing { "description": "" } should produce a link with { "description": null }. Any links I retrieve with GET api/links should ensure the description is either null or non-empty.
The text was updated successfully, but these errors were encountered:
When creating links with the API, omitting the
description
key entirely or passing{ "description": null }
produces a link with"description": null
. However if I pass an empty string ({ "description": "" }
) I get back a link with"description": ""
. AFAIK this doesn't affect the behavior of the link redirector, but it is annoying from an API perspective as it means I have to check if the description is empty instead of just checking if it's non-null.Expected behavior:
Passing
{ "description": "" }
should produce a link with{ "description": null }
. Any links I retrieve withGET api/links
should ensure the description is either null or non-empty.The text was updated successfully, but these errors were encountered: