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
{{ message }}
Repository navigation
Commit 0fa1294
Browse filesBrowse the repository at this point in the historyBrowse files
✨ Leave out a prop whose expression produced nothing (#537) (#541)
An ordinary component's expression prop that evaluates successfully to
`undefined` is now absent rather than rejected: the omission happens in the
one resolver both Markdown and function components pass through, before
validation, so an optional prop stays unset, a declared default applies, and a
required one fails as missing with no body run. `null`, evaluation failures,
non-serializable roots, nested normalization, captures and `<Let value>` are
unchanged, and nothing durable holds `undefined`.
The scanner keeps an ordinary component's literal `{undefined}` as an
expression so it reaches that same resolver; a construct's arbitrary-value
operand keeps its scan-time reading.
One authored `<PullRequest number={pullRequest.number}>` inside a bounded loop
now creates without a number and then updates the number it created.
Co-authored-by: Taras Mankovski <[email protected]>
0 commit comments