You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the search bar on Flagr is limited to searching tags and descriptions. It would be nice if you could also search for specific constraints, i.e. searching for a specific constraint property name (property:property-name).
I ran into a case where I was modifying a method used to assign a value to a constraint property, and I had to manually check every single flag to see if that property was being used to make sure I wouldn't break anything. Adding this feature would save a lot of time in the future :)
The text was updated successfully, but these errors were encountered:
This allows me to search on a property of the Flag.
This can only work on the properties loaded on the client.
If support for more properties is need one solution would be something like Riot (Go search library) and implementing search server side. This would allow searching on all properties across larger datasets. But is a more involved solution.
This fixes a few minor issues around string trimming. Previously spaces after commas were included in the match and failed to match.
Working on some unit tests and documentation now. Setting up Jest for the project and this refactor 😬
Some other considerations.
Might want to update UI packages as they're major versions behind and a few audit warnings
Setting up @vue/test-utils to test some of the interface could be 👌🏽
Currently, the search bar on Flagr is limited to searching tags and descriptions. It would be nice if you could also search for specific constraints, i.e. searching for a specific constraint property name (
property:property-name
).I ran into a case where I was modifying a method used to assign a value to a constraint property, and I had to manually check every single flag to see if that property was being used to make sure I wouldn't break anything. Adding this feature would save a lot of time in the future :)
The text was updated successfully, but these errors were encountered: