-
Notifications
You must be signed in to change notification settings - Fork 1
Twitter option #1
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
base: master
Are you sure you want to change the base?
Conversation
|
Nice, thanks! I'm not the original author, so I'm not too familiar with the core. I was hoping my fork would be merged into the author's but I'm not hopeful at this point, so it is probably safer for people to use this fork due to the XSS fix. How confident are you about these changes / refactorings? If you wouldn't mind telling me how to run the Coffee tests, I'll add one or two myself for our use cases / the XSS. |
|
Yeah, I'm glad I saw your fork and so I began with this. Anyway, I just If you have CoffeeScript installed, just run "coffee test/test.coffee" (tbh On Fri, Sep 16, 2011 at 12:13 AM, Mike Rooney <
|
This fork adds a twitter option:
linkify('@mahemoff', { twitter: true })
becomes
< a href="http://twitter.com/mahemoff" title="http://twitter.com/mahemoff" > @mahemoff < /a >
(not sure if the angle brackets are about to be mangled when I submit this comment...)
In doing so, there's some refactoring to simplify the way the uber URI regexp is built up.
There's also some basic support for Node and a tiny test (in CoffeeScript).