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
Is your feature request related to a problem? Please describe.
If cell.getValue() can not find a value in the row using the specified accessorKey it prints a warning for each part of the key that returns undefined. We're using EdsDataGrid on a dataset where there is no guarantee that every column exists in every row. The console fills up with, what is in our case, unnecessary warnings.
Describe the solution you'd like
It would be nice if we could specify default/fallback values in the column config that will be displayed if the accessorKey returns undefined on the current row. Or a bool flag, i.e lignoreUndefined: true to prevent warnings. Example:
Is your feature request related to a problem? Please describe.
If
cell.getValue()
can not find a value in the row using the specifiedaccessorKey
it prints a warning for each part of the key that returnsundefined
. We're usingEdsDataGrid
on a dataset where there is no guarantee that every column exists in every row. The console fills up with, what is in our case, unnecessary warnings.Describe the solution you'd like
It would be nice if we could specify default/fallback values in the column config that will be displayed if the
accessorKey
returnsundefined
on the current row. Or abool
flag, i.e lignoreUndefined: true
to prevent warnings. Example:Describe alternatives you've considered
We have been using column configs like this:
It will display
-
for values that does not exist, letting us differentiate between non-existing properties and empty properties.To prevent the warnings we have made the following workaround:
The text was updated successfully, but these errors were encountered: