Skip to content

Check for !== undefined to avoid treating false as not resolved#189

Merged
NullVoxPopuli merged 1 commit into
universal-ember:mainfrom
piemonkey:resolving-false
Apr 22, 2026
Merged

Check for !== undefined to avoid treating false as not resolved#189
NullVoxPopuli merged 1 commit into
universal-ember:mainfrom
piemonkey:resolving-false

Conversation

@piemonkey
Copy link
Copy Markdown
Contributor

I came across an issue with trackedFunction wrapping a function that returns Promise<boolean>. The State class' state() getter and the isResolved() method were both mistakenly treating a falsy value as 'not resolved'. Since the internals return undefined before the promise resolves, I replaced the logic with a !== undefined check. This would still fail if the wrapped function returns Promise<truthy | undefined>, but at least this handles false or null and does not modify any other behaviour.

@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 22, 2026

@piemonkey is attempting to deploy a commit to the universal-ember Team on Vercel.

A member of the Team first needs to authorize it.

@NullVoxPopuli NullVoxPopuli added the bug Something isn't working label Apr 22, 2026
@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 22, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
reactive Ready Ready Preview, Comment Apr 22, 2026 1:38pm

@NullVoxPopuli NullVoxPopuli merged commit b7da7a9 into universal-ember:main Apr 22, 2026
17 of 19 checks passed
@github-actions github-actions Bot mentioned this pull request Apr 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants