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
Currently, this library replaces empty field values with either {} or a null prototype. This inconsistency leads to hard-to-debug scenarios in Next.js especially due to the isomorphic nature of data.
Expected Behavior
Nullish fields should return null instead and empty object which is truthy in fact.
Actual Behavior
Either an empty object {} or a null prototype set as fallback for empty values.
Possible Fix
Replace all fallback mechanisms to add null instead of the objects.
Steps to Reproduce
Request an entry with empty value
Witness fallback replacement
Context
Turned out this to be an issue when passing data in RSCs using Next.js 14.
Your Environment
Version used: 0.2.3
Environment name and version (e.g. Chrome 39, node.js 5.4): Node 20, Browser (Chrome), Next.js 14
Operating System and version (desktop or mobile): OSX
Link to your project: private
The text was updated successfully, but these errors were encountered:
Description
Currently, this library replaces empty field values with either
{}
or a null prototype. This inconsistency leads to hard-to-debug scenarios in Next.js especially due to the isomorphic nature of data.Expected Behavior
Nullish fields should return
null
instead and empty object which is truthy in fact.Actual Behavior
Either an empty object
{}
or a null prototype set as fallback for empty values.Possible Fix
Replace all fallback mechanisms to add
null
instead of the objects.Steps to Reproduce
Context
Turned out this to be an issue when passing data in RSCs using Next.js 14.
Your Environment
The text was updated successfully, but these errors were encountered: