-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
Allow underscores #6
Comments
Ah right, makes sense! retext-syntax-mentions/index.js Line 9 in 65b5811
the code is currently made specifically for GH, e.g., also to support teams: |
You made it for GitHub so I would prefer b :) Another solution would be to give an option to pass a custom regex. btw I also miss a package for supporting hashtags which would be very similar to this one. But this is out of scope here. |
Yah, this project was specifically made for https://github.com/github/opensource.guide, and I’m using it on all our readmes, so typically stuff that renders on GH or like that, so indeed, no twitter handles! Re b), vaguely worded, but I meant to question whether people would use I think passing in a new regex makes sense. And a boolean option for whether to support teams? So then, accept a Do you know what the syntax for twitter handles is? |
I'm building a markdown writing app with spell checks etc. So I don't know which kind of mention will may be used. I would love to support just some kind of "generic" mention. So when adding a style option with syntax for twitter handles:
|
So
Teams unfortunately can’t be matched with a regex, as retext-syntax-mentions/index.js Lines 31 to 36 in 65b5811
So, in your writing app, what should happen if someone were to use a GH-style mention of |
Ah okay, makes sense.
I want to prevent that |
Teams wasn’t needed! Released in 2.1.0. See docs for more info. |
great! thank you! 🙌 |
Since Twitter also allows underscores in the username, it would be nice if this is would also be supported by this package.
@_philippkuehn
(my twitter handle) is not recognized.The text was updated successfully, but these errors were encountered: