Open Khaan25 opened 2 days ago
Same in the "Create New Key" form. You can use whitespaces only in most of the inputs. I think both can be fixed in one PR.
https://github.com/user-attachments/assets/5a9d34b6-05b6-42a0-8572-073c4f657cdb
The real challenge begins when you attempt to delete an API like that 😈
https://github.com/user-attachments/assets/41b8ecc4-0c95-4732-a5be-533ae88174a1
💀
@chronark I think this is a critical issue, I would like to work on it and make sure all inputs in the application are properly validated on frontend as well as the backend.
What do you say?
Please note that there may be conflicts with the open PRs addressing other input-related issues, such as this one: #2319. FMPOV, it's important to carefully validate the fixes before combining them into one.
Preliminary Checks
[X] I have reviewed the documentation: https://unkey.com/docs
[X] I have searched for existing issues: https://github.com/unkeyed/unkey/issues
[X] This issue is not a question, general help request, or anything other than a bug report directly related to Unkey. Please ask questions in our Discord community: https://unkey.com/discord.
Reproduction / Replay Link (Optional)
No response
Issue Summary
I was testing the app core functionality. I found out that I can create a API without a name:
Steps to Reproduce
Expected behavior
This dialog form should have some sort of input validation and sanitation to valid the user data.
I follow "NEVER TRUST THE USER" :)
It should give some sort of error to enter a proper name, you can also use .trim() function to get rid of the spaces :) I can also solve this issue.
Other information
No response
Screenshots
See my cursor in the image:
Version info