Consider using a string similarity algorithm: levenshtein to optimize the search experience
I-Want-ToBelieve opened this issue · comments
@KycKyc can you tell me where is the items data (field in SeekerProps) in the network request
interface SeekerProps<Item> {
...
items: Item[];
...
}
@KycKyc can you tell me where is the items data (field in SeekerProps) in the network request
interface SeekerProps<Item> { ... items: Item[]; ... }
@I-Want-ToBelieve I believe you're trying to look for the items endpoint
if you want to feed it with "something" and test results, you can use:
type Item = {
id: string;
group: string;
name: string;
};
adding a *
or not doesn't affect the result of regex matching, it gives the exact same groups
the regex here is used for splitting user's input and match with item names
e.g. user input N S
, it will be splitted into [N,S]
and (^|.*?\s)(N)(^|.*?\s)(S)
can also match with Nekros Prime Set
even without the *
thus, I'm going to close this issue, you can open another issue for other suggestions