How to suppress/disable "deeply nested key returned undefined" warning

[MattChowski]

Hello!

This seems to be a rather simple question but no idea how to solve it. From our backend, some values can return "undefined", I do handle this case in the table so nothing breaks.

Being fully aware of this issue, I'd like to remove the warning from the console as it obstructs other messages. Is there any way to do so? I have no ways to change the values from the backend to return null instead.

I've tried to look for the issue and the only thing I found is that this used to log an error instead of a warning and decision has been made to keep the warning.

Thanks in advance!

[devthub]

DO you have any work around for this?

[MattChowski]

Nope

[KevinVandy]

You can use an accessorFn instead of the string accessorKey. In your accessorFn, you can handle the undefined checks how you want.

[danikane]

That's what I ended up with then I saw this answer. :)

[briavicenti]

This is also an issue for us. Our tables have placeholder logic to show a dash in the event that a given row value is undefined, and so we don't benefit from the warnings being thrown. I implemented a custom accessorFn that uses the Lodash _.get helper to retrieve a field's value with a nested key, but it would have been nice to use the React-Table's built-in functionality for this instead!

[strimbob]

bump! i also think this warning should be configurable , it is super annoying.I implemented a custom accessorFn too

[martinliptak]

What's the point of showing the warning? Just handle it the same way as null. For example, we show a list of orders along with their supplier's name. Some orders don't have a supplier so "supplier.name" is undefined. I don't find any value in the warning.