Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Audit and consolidate usage of null and undefined in the engine #4105

Open
jmsjtu opened this issue Mar 27, 2024 · 1 comment
Open

Audit and consolidate usage of null and undefined in the engine #4105

jmsjtu opened this issue Mar 27, 2024 · 1 comment

Comments

@jmsjtu
Copy link
Member

jmsjtu commented Mar 27, 2024

In several parts of @lwc/engine-core we have inconsistent usage of whether a missing vnode or its value is undefined or null.

We should audit all usages and consolidate into using either undefined or null.

@nolanlawson
Copy link
Contributor

I think typically undefined is used for missing primitives (numbers, strings, etc.) whereas null is used for missing objects. I dunno if this has an impact on JS engine performance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants