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

Replacing clj-fuzzy library with talisman #44

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

csp197
Copy link

@csp197 csp197 commented Oct 27, 2023

This PR replaces the clj-fuzzy library with the talisman library.
I believe this should resolve the error seen in #43

The talisman library offers two separate jaro based metrics, jaro and jaro-winkler.
In this PR, I imported jaro, but this can be updated as needed.

@csp197 csp197 changed the title Replacing cli-fuzzy package with talisman Replacing clj-fuzzy package with talisman Oct 27, 2023
@csp197 csp197 changed the title Replacing clj-fuzzy package with talisman Replacing clj-fuzzy library with talisman Oct 27, 2023
Copy link

@imbergman imbergman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

@stevemckenzie
Copy link

Works for me!

@jonrose-dev
Copy link

We're running into this issue as well. Is there any timelines when this can be merged in and released?

@0x80
Copy link

0x80 commented Feb 15, 2024

Looks very much like this project has been abandoned. Time fork and republish under a different scope name maybe. I am considering it.

Other than that, it seems that this PR made a mistake by adding the talisman as a dev dependency.

@0x80
Copy link

0x80 commented Mar 8, 2024

@csp197 have you tried running the tests after your change? It seems 2 of them are failing

@0x80
Copy link

0x80 commented Mar 8, 2024

I have forked and published a more modern version of this. I didn't yet add the Talisman replacement, because of the failing tests.

I am using this in a typescript project and didn't experience the bug #43 but possibly I'm using it differently.

See #47

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

Successfully merging this pull request may close these issues.

5 participants