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
In 2.x and (behind a compatibility feature flag) in 3.x it was possible to let the JsonContentObject (JSON) return null instead of an empty array.
I'd like to propose a new flag ifEmptyReturnNull for that JSON cObject. A flag with that name is already present for rendering the fields, which is cool and should be kept that way!
@kitzberger in 4.x by default dataProcessing is returning null instead of array, no flag needed, flag was meant for already built apps only so they won't break
In 2.x and (behind a compatibility feature flag) in 3.x it was possible to let the
JsonContentObject
(JSON) returnnull
instead of an empty array.I'd like to propose a new flag
ifEmptyReturnNull
for that JSON cObject. A flag with that name is already present for rendering the fields, which is cool and should be kept that way!Here's an example to back my proposal: JSON's always rendering an empty array instead of the IMHO more correct
null
in case no record can be fetched:The text was updated successfully, but these errors were encountered: