API Setting : "Default Prefix" Field Should Not Allow Only Whitespace Values

[Vardhaman619]

Preliminary Checks

• I have reviewed the documentation: https://unkey.com/docs

• I have searched for existing issues: https://github.com/unkeyed/unkey/issues

• 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

The Default Prefix field for API currently allows input consisting solely of whitespace (e.g., spaces, tabs). This can lead to confusion or hidden issues since whitespace is not easily visible, and the system saves it as a valid prefix. There should be validation to ensure that a valid prefix contains at least one non-whitespace character.

Steps to Reproduce

1. Navigate to Dashbaord -> APIs -> Select anyone API -> API Settings
2. Enter only whitespace (e.g., several spaces) in the "Default Prefix" field.
3. Attempt to save the changes.
4. Observe that the system saves the field without validation.

Expected behavior

The Default Prefix field should not accept input with only whitespace. A validation error should be shown if the user tries to save the field with just spaces or tabs. The field should require at least one visible character before allowing the user to save.

Other information

Actual Result:

The system allows saving the field even when it contains only whitespace.

Expected Result:

A validation error should appear, prompting the user to enter a valid prefix with at least one non-whitespace character.

Screenshots

video.webm

Version info

.

[linear]

ENG-1410 API Setting : "Default Prefix" Field Should Not Allow Only Whitespace Values

[bikaxh01]

/assign

[Vardhaman619]

@bikaxh01 , I’m already working on this issue. I’m just waiting for the label to be assigned so I can officially start.

[harshsbhat]

@Vardhaman619 it's also a problem in the create key trpc route. But wait for approval.

So you will need to validate it for both default prefix and create key.

[perkinsjr]

/award 150

[oss-gg]

Awarding Vardhaman619: 150 points 🕹️ Well done! Check out your new contribution on oss.gg/Vardhaman619

[Vinod-Mane3021]

/assign

[oss-gg]

Assigned to @Vinod-Mane3021! Please open a draft PR linking this issue within 48h ⚠️ If we can't detect a PR from you linking this issue in 48h, you'll be unassigned automatically 🕹️ Excited to have you ship this 🚀

[YASH-YADAV-dynamo]

/assign

[oss-gg]

This issue is already assigned to another person. Please find more issues here.

[Haritscode]

/assign

[oss-gg]

This issue is already assigned to another person. Please find more issues here.

[Usmanxs]

/assign

[oss-gg]

This issue is already assigned to another person. Please find more issues here.

[chronark]

It should actually not allow any whitespace at all