haggen/localthreat

Apostrophe being ignored by ESI search endpoint

haggen opened this issue · 4 comments

haggen commented

Example:

  • Lords Servant
  • Lord's Servant

Both searches return the same result: IDs for both characters.

haggen commented

Have to come up with something since it won't be fixed. esi/esi-issues#211 (comment)

haggen commented

There have been lots of cases like this I should come up with some kind of mitigation, perhaps:

  • Add all the characters returned in the search result. It'll add extra non-related characters to the list but it might be than getting the wrong character. Or...
  • Prompt the user to resolve the ambiguity by selecting the characters they want to actually fetch. Though it might be too obtrusive for a tool that should be practical.
haggen commented

Might get solved with #18