You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I was just adding my adventure to "EPCOT". But couldn't wind it on the automatic description generator, because Wikipedia wrote it "Epcot". This is innocent enough, but it also doesn't find "Disney Land" if it's written "Disney land", which is incredibly annoying. I know there could be all kinds of different improvements possible, like ignoring commas and parentheses, but as a minimum, could we make the comparison case insensitive?
Describe the solution you'd like
Make the Wikipedia search case insensitive.
Describe alternatives you've considered
Could do other string sanitation, or even use a fuzzy matcher like the hamming distance. But case insensitivity would already fix the most annoying parts.
The text was updated successfully, but these errors were encountered:
Just fixed this in the dev branch. What I did was have it actually do a search first for articles, then it takes the name of that first article to pass into the search because it is case sensitive.
Is your feature request related to a problem? Please describe.
I was just adding my adventure to "EPCOT". But couldn't wind it on the automatic description generator, because Wikipedia wrote it "Epcot". This is innocent enough, but it also doesn't find "Disney Land" if it's written "Disney land", which is incredibly annoying. I know there could be all kinds of different improvements possible, like ignoring commas and parentheses, but as a minimum, could we make the comparison case insensitive?
Describe the solution you'd like
Make the Wikipedia search case insensitive.
Describe alternatives you've considered
Could do other string sanitation, or even use a fuzzy matcher like the hamming distance. But case insensitivity would already fix the most annoying parts.
The text was updated successfully, but these errors were encountered: