[GH-ISSUE #5271] [feature]: create workspace should be at latest 6 character #2015

New issue

Closed

opened 2026-03-16 22:51:52 +03:00 by kerem · 3 comments

kerem commented

2026-03-16 22:51:52 +03:00

Owner

Originally created by @faritor on GitHub (Jul 23, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5271

Originally assigned to: @nivedin on GitHub.

Is there an existing issue for this?

I have searched the existing issues

Summary

thank you to the developer team for providing such an excellent product

as the title suggests, it should be at least six characters, but it may not be appropriate when the content of the workspace name is in Chinese, Japanese, Korean, or other non-alphabetic types of text

Why should this be worked on?

check the Unicode encoding of each character. If the encoding is greater than 255, it is considered that the character may be Chinese, Japanese, Korean, etc.

another thing is to allow editing or customizing the name of the instance if possible.

Originally created by @faritor on GitHub (Jul 23, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5271 Originally assigned to: @nivedin on GitHub. ### Is there an existing issue for this? - [x] I have searched the existing issues ### Summary thank you to the developer team for providing such an excellent product as the title suggests, it should be at least six characters, but it may not be appropriate when the content of the workspace name is in Chinese, Japanese, Korean, or other non-alphabetic types of text ### Why should this be worked on? check the Unicode encoding of each character. If the encoding is greater than 255, it is considered that the character may be Chinese, Japanese, Korean, etc. another thing is to allow editing or customizing the name of the instance if possible.

kerem

2026-03-16 22:51:52 +03:00

closed this issue
added the
feature
label

kerem commented

2026-03-16 22:52:08 +03:00

Author

Owner

@hardik118 commented on GitHub (Aug 16, 2025):

@faritor @abraham @silentmatt Hi, I’d love to work on this issue! Could you please assign it to me?

@hardik118 commented on GitHub (Aug 16, 2025): @faritor @abraham @silentmatt Hi, I’d love to work on this issue! Could you please assign it to me?

kerem commented

2026-03-16 22:52:13 +03:00

Author

Owner

@faritor commented on GitHub (Aug 23, 2025):

@faritor @abraham @silentmatt Hi, I’d love to work on this issue! Could you please assign it to me?

thank you for your reply. I'm looking forward to optimizing this restriction.

@faritor commented on GitHub (Aug 23, 2025): > [@faritor](https://github.com/faritor) [@abraham](https://github.com/abraham) [@silentmatt](https://github.com/silentmatt) Hi, I’d love to work on this issue! Could you please assign it to me? thank you for your reply. I'm looking forward to optimizing this restriction.

kerem commented

2026-03-16 22:52:18 +03:00

Author

Owner

@jamesgeorge007 commented on GitHub (Sep 11, 2025):

Hi, closing this issue as the 6-character restriction on workspace names has now been lifted.

@jamesgeorge007 commented on GitHub (Sep 11, 2025): Hi, closing this issue as the 6-character restriction on workspace names has now been lifted.

kerem referenced this issue

2026-03-16 23:17:43 +03:00

[GH-ISSUE #5523] [bug]: crypto.subtle is missing in Pre-request script envrironment. #2130

kerem referenced this issue

2026-03-17 02:48:31 +03:00

[PR #5791] [MERGED] feat(js-sandbox): add extensive Web Crypto API support #5351