Skip to content

Undefined is not the same as falsy #4103

Closed

Description

There's an undefined check on route arguments but it's not actually checking for undefined:

image

This causes an issue if the value is anything that would return falsy (0, empty string, false).

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

Metadata

Assignees

Labels

TypeScriptPull requests that update Javascript codeWIPhelp wantedIssue caused by core project dependency modules or librarytype:bugA broken experience

Type

No type

Projects

  • Status

    Done ✔️

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions