Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Select filter not working properly
See original GitHub issueSimilar issue to #517
I have the following table with a select filter on the currency column:
When I use an object like this: { 0: 'EUR', 1: 'AUD', 2: 'CAD' } , in the options
as in the examples: {0: 'bad', 1: 'good'}
the filter does not match any of the rows in the table:
If I set string values as keys (same as the value), e.g. { 'EUR': 'EUR', 'AUD': 'AUD', 'CAD': 'CAD' }, only then it works properly:
If it’s not working as it should, maybe the examples/docs should be updated, showing string values as keys in the option object instead of numbers.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I made the same mistake/overlook on the key types. Thanks for all the posts here. Got my selectFilter working 😃
Yes, that’s exactly the example I saw. You’re right, I didn’t notice that quality was a number… Thank you very much for the quick response! I already made it work making the key the same as the value, as I said before. I thought I should report it, as I thought it was supposed to be functioning with numbers as in the example. Keep up the good work! 😃