-
Notifications
You must be signed in to change notification settings - Fork 5.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
URL Scalar #4640
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Is this still valid? What's the downside of using a string for URLs in GraphQL? |
The idea behind this scalar was to have unified URL validation. |
We need to refactor URL in API by introducing URL Scalar because in some part of GraphQL Api we using string type to handle URL. Mutation like
SetPassword
orDeleteAccount
have URL as argument.The text was updated successfully, but these errors were encountered: