-
Notifications
You must be signed in to change notification settings - Fork 200
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
Segment search in match rule doesn't work #462
Comments
Thanks for the bug report @hagaishapira ! I can confirm this same behavior. I will look into trying to fix this, likely an issue with the javascript library i'm using (buefy) to render this search |
@hagaishapira just fixed this in #475 and released a new version |
Thanks Mark, we will! Appreciate your hard work.
…On Mon, 14 Jun 2021, 18:19 Mark Phelps, ***@***.***> wrote:
@hagaishapira <https://github.com/hagaishapira> just fixed this in #475
<#475> and released a new version
1.3.0. please give it a try! and thanks again for the bug report
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#462 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AG6SIF7REUOUBUXNRCH2B2LTSYMZ3ANCNFSM46AZKSFA>
.
|
@markphelps works great! This is has been a major pain point for the team for weeks now, we are all rejoiced. |
Great! glad to hear! It would be amazing if your company was able to help sponsor Flipt's development |
Describe the bug
When setting up a new rule and looking for a segment to match typing anything doesn't seem to search or offer appropriate segments to match.
Version Info
v1.2.1
To Reproduce
Expected behavior
I expect that only appropriate segments that matched my typed input will show up in the dropdown list.
Screenshots
See how while I typed "hagai" I see the same results I've seen before typing anything.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: