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

Trace - allow for similar fuzziness that vaasatog uses? #32

Open
Villawhatever opened this issue Feb 3, 2025 · 2 comments
Open

Trace - allow for similar fuzziness that vaasatog uses? #32

Villawhatever opened this issue Feb 3, 2025 · 2 comments

Comments

@Villawhatever
Copy link

Villawhatever commented Feb 3, 2025

If a user searches for Crew or 702.122, search for 702.122a since that's the relevant thing.

@lunakv
Copy link
Owner

lunakv commented Feb 4, 2025

Good idea. Couple of notes for my future self:

  • I plan to change the glossary "get rule" API from fuzzy by default to exact by default. The trace API should use the same convention.
  • The help text on the trace page has to be updated accordingly.
  • There should probably be some visible warning whenever such a redirect occurs. I'll have to think of how that'll look.

@lunakv
Copy link
Owner

lunakv commented Feb 16, 2025

Support for redirection from the base rule has been added in #34 and lunakv/academyruins-api#76 (see example trace). Redirection from a keyword is a little more complex, so I'm postponing that for later.

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