An row containing a null property would throw, as null is an object but Object.entries() does not support null
searchFields prop defaulted to null but it was assumed to be an array
This also introduces the first fully mounted component test. The test simulates user rather than programatic interaction with this component, and represents the real world use case better. The majority of the existing unit tests calling the components methods and computed properties directly, will become the responsibility of the search/filter service when this is introduced (see description in #85).
Addresses two bugs introduced in https://github.com/flowforge/forge-ui-components/pull/85
nullproperty would throw, asnullis an object butObject.entries()does not support nullsearchFieldsprop defaulted tonullbut it was assumed to be an arrayThis also introduces the first fully mounted component test. The test simulates user rather than programatic interaction with this component, and represents the real world use case better. The majority of the existing unit tests calling the components methods and computed properties directly, will become the responsibility of the search/filter service when this is introduced (see description in #85).