Skip to content

collect unmatched tokens#15

Open
stereosteve wants to merge 1 commit into
kitspace:masterfrom
stereosteve:unmatched
Open

collect unmatched tokens#15
stereosteve wants to merge 1 commit into
kitspace:masterfrom
stereosteve:unmatched

Conversation

@stereosteve

Copy link
Copy Markdown

Hello Kaspar,

One thing that might be nice is the ability to collect the extraneous tokens, so that if user enters 100nF 0603 50V Kemet, the Kemet token could be used for full text search.

This is a pretty hack-y way to do it, and it breaks the return behavior of {} for no match. I've not used Nearly before, so believe there is probably a better way to do this, but thought I would create PR just to get your thoughts.

@kasbah

kasbah commented Aug 24, 2018

Copy link
Copy Markdown
Member

Hi Steve, I was playing around with something similar quite a while back on the return-ignored branch. It did what you implemented but also checked if any input caused no change to the output. I believe it still fails on some edge cases.

There is a demo up as well. Should have opened a pull-request for visibility. The way you just add it as a prop on the return object is neater more backwards compatible than what I did though.

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.

2 participants