The logic is fine. If you rename the variable to isAdmin, it makes perfect sense. Either they are an admin, or they are not an admin, or the state is unknown (here expressed as null). If you want to throw another JS-ism at this, undefined could be assigned before the check has been made.

I regularly use variables like this. If users is undefined, I haven’t fetched them yet. If they’re a list, then fetching is complete. If they’re null, then there was an error while fetching.

Today i have seen:

if (var === true || var === 'true' || var === "true")

I'm just fortunate enough to not work with the frontend at our very backend service, but I always hear things that shouldn't be even allowed in this planet.

Yes JS is the crime in itself.

Not yes or no, but a secret third thing

How many "equal" symbols do we need to be absolutely sure?

Like any good Boolean:

True / False / File not found

Just use an enum lol

True, false, and magic.

Obviously this should be a Result that the gets compiled to a nullable bool.

Aren't the first two if branches completely useless? The variable was just defined without a value, so it should always be null

the real crime in this photo is the ===

I'm so confused. I understand the reasoning behind two equal signs but three?