Block emoji from being entered as a repo name
See original GitHub issueEmoji shouldn’t be allowed in place of a repo name as they are converted anyway to “normal” characters by GitHub.com and Desktop once published.
If you already have a repo with the namegithub.com/tierninho/-1
and you decide to create a new repo with an emoji 🐴 as the repo name, the name becomes converted to “normal” characters as expected. However, if you click “open in GitHub” or “create PR”, the existing repo is opened despite the real url being github.com/tierninho/-
Just remove the Emoji option from the Edit menu?
tested 1.0.5beta0, mac
Issue Analytics
- State:
- Created 6 years ago
- Comments:10 (7 by maintainers)
Top Results From Across the Web
How to disable emoji from being entered in Android EditText?
There is nothing that will 100% disable emoji. The keyboard can act to any mode it sees in whatever way it thinks best,...
Read more >How to block emojis from entering UITextView - YouTube
Swift / UIKit / UITextViewIn this video we look at a couple of different ways to block emojis from being entered into a...
Read more >Icons, Emojis - Material for MkDocs - GitHub Pages
Tip: Enter some keywords to find icons and emojis and click on the shortcode to copy it to your clipboard. Configuration¶. This configuration...
Read more >Input validation in Jetpack Compose | by Denis Rudenko
By default it's NAME, since it's the first input from top to bottom. init{} block checks if there is last known focused TextField,...
Read more >Xamarin.Forms Editor - Microsoft Learn
Set and read text; Set placeholder text; Prevent text entry; Transform text ... <Editor x:Name="editor" Text="I am an Editor" />. In C#:.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@outofambit Sounds great! I have the changes ready and will get a pull request ready soon.
I certainly agree. I was hoping that perhaps this might be an opportunity for some improved documentation to explain this, so I gave it a mention while it was relevant.
@Daniel-McCarthy that seems like a sensible approach to me. I’m not sure about the reasoning for filtering out
_
so I think its best to preserve that behavior for now. thank you!