Skip to content
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

getDescription Regex is too lenient #6

Closed
thedamon opened this issue Mar 23, 2015 · 2 comments
Closed

getDescription Regex is too lenient #6

thedamon opened this issue Mar 23, 2015 · 2 comments

Comments

@thedamon
Copy link

if I have in my JSON
{"term": "black cat", "description":"a black feline"},
{"term": "cat", "description": "meow"}

Anywhere I use the word "cat" I get the description "a black feline", unless I place the "cat" definition above "black cat" in my JSON file. Since we're splitting terms by commas, shouldn't getDescription behave the same way?

@rmdort
Copy link
Contributor

rmdort commented Jun 4, 2015

I cant replicate this issue. Have you tried it with the latest version?

If not, can you create a fiddle

@thedamon
Copy link
Author

Hmm I'll have to double check this but thanks for looking into it!

I tried to throw together a jsfiddle but it was not happening with the github links and a json file in a gist. Is there a service you've had luck with for that?

@rmdort rmdort closed this as completed Sep 7, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants