-
Notifications
You must be signed in to change notification settings - Fork 222
filterFunction of a custom component is returning string "object Object" #379
Comments
Hey, I'd suggest you build a 'proper' table using |
Sorry man, that's right. Will do it the proper way! Thanks! |
@andrewlorenz + @Ricardonacif can either of you elaborate on this solution? Are you saying skip using reactable? Or some table alongside? |
hi there, no I didn't mean not to use reactable! just to do a bit more coding to enable the filtering than expecting it to be done for you by reactable. I found that there are a couple of ways to feed reactable with (a) the data you want the user to see and (b) the data you want to be available for use in filtering. Especially useful when you want to apply formatting to the data but filter it in its raw state. |
Hey @andrewlorenz ! Thank you for the offer! The data isn't so complicated that it would be difficult to filter and format but a nice generic method that works with how it's already being structured to display in the component is more straightforward for at least some of our usages 😉 |
For anyone reading this, the probable reason for getting [Object Object] is that you have set a |
If I'm understanding you correctly this also occurs for me with one child element because of #378. The fork I mentioned can be found here: https://github.com/Adorkable-forkable/reactable |
hi yes its entirely possible, and I just realised my comment doesn't relate specifically to this issue. So that fork you mention, are you intending to keep that one maintained (unlike this one which is sadly going to seed I fear) |
Unfortunately I don't think I'll be able to maintain the fork in a real way either, for anyone interested it'd be best if they pulled the change ;) |
Guys, I have a column where I render a custom component. When I try to use the filterFunction to specify how I wanna filter, the "contents" is coming as a string "object Object". ```
Am I doing something wrong?
The text was updated successfully, but these errors were encountered: