Property grid hide null values feature removes boolean switch.

[mathieu-fournier]

PropertyGridComponent ShowHideNullValuesSettingsMenuItem feature hides boolean switches.
Unless I dont understand the feature properly, a boolean is not a null value and should not be hidden.

See in the image below, the "Add central parking" boolean toggles get's removed.

Thanks.

[JonasDov]

@mathieu-fournier, I have a question about the ShowHideNullValuesSettingsMenuItem component.

Component name says "null values", but its label reads "Show/Hide Empty Values" and it currently hides empty strings ("") too, not just null/undefined. So the component name doesn't match its rendered label and behaviour.

Do you need a component which hides only null/undefined values, or empty values in general (including empty strings)?

[grigasp]

Do you need a component which hides only null/undefined values, or empty values in general (including empty strings)?

@noelgonzalezjones, could you comment on this, too? At the moment the menu item is labeled "Show/Hide Empty Values" and filters-out all falsy values, including empty strings, 0, false, etc. The latter two are a clear bug, as they're definitely not "empty". But we're not sure about empty strings - do users differentiate between empty string vs null string?

[mathieu-fournier]

@JonasDov
I'm not sure. Depends on what purpose/value this feature has for users.
We could even hide more than "empty" values. Maybe, depending on the use-case, non-empty values, like code, ECInstanceId, and more could be expected to be hidden as well.
Do we even have a use-case for this feature right now ? In OS+, it's currently disabled, I happened to try it out while debugging errors, so might be a non-issue or a feature we can remove altogether...

[noelgonzalezjones]

@grigasp Good question. From an end-user perspective, I don't think users differentiate between an empty string and a null/undefined value, in both cases they just see a blank field. So for the purposes of this toggle, I'd treat them the same and hide both.

But one important point is that "0" and/or "false" should never be hidden. Those are valid, intentional values that users need to see. A boolean set to "false" or a numeric value of "0" is meaningful data, not an empty field.

So the toggle should hide null, undefined, and empty strings, but preserve "0", "false", and any other non-empty values.

Hope that helps.

[JonasDov]

@mathieu-fournier The fix should be available in 1.20.0. To consume it, a simple version bump should be enough.
I'd also recommend switching from the deprecated APIs to their replacements:

• ShowHideNullValuesSettingsMenuItem -> ShowHideEmptyValuesSettingsMenuItem;
• NullValueSettingContext -> EmptyValuesSettingContext.

Please let us know if you encounter any issues.