True crime
-
a === breturns true ifaandbhave the same type and are considered equal, and false otherwise. Ifaisnullandbis a boolean, it will simply return false.I see, so logically it is fine.
Just not in the context. -
My preferred way of modelling this would probably be something like
role: "admin" | "regular" | "logged-out"
or
type Role = "admin" | "regular";
role: Role | null
depending on whether being logged out is a state on the same level as being a logged-in (non-)admin. In a language like Rust,
enum Role {Admin, Regular}
instead of just using strings.I wouldn't consider performance here unless it clearly mattered, certainly not enough to use
role: number,
which is just about the least type-safe solution possible. Perhaps
role: typeof ADMIN | typeof REGULAR | typeof LOGGED_OUT
with appropriately defined constants might be okay, though.Disclaimer: neither a professional programmer nor someone who regularly writes TypeScript as of now.
wrote last edited by [email protected]Yeah obviously with constants for the set roles per value. Some languages call them enums, but the point is that what we pass and use is always still the smallest integer type possible. With the extra bonus that if the roles ever become composable, the same value type would likely suffice for a bitflag and only thing needing refactoring would be bitshifting the constants.
But anyway, this turns out to be the weirdest hill I find myself willing to die on.
-
Depends on your requirements.
If the admin status needs to be checked in a database, but most actions don't require authentication at all, it's pointless to waste resources checking and it would be left null until the first action that needs the information checks it and fills it in as true or false.
I don’t really follow you there, wouldn’t it be exactly the opposite and wouldn’t checking for nulls be, as a premise, more wasteful? But doesn’t really matter, time to digress. I’m conventionally educated as an engineer so what I know and find reasonable today might be outdated and too strict for most contemporary stuff.
-
Ah, the ol' tristate boolean switcheroo
wrote last edited by [email protected]tristate as in three states or tristate as in five states?
-
tristate as in three states or tristate as in five states?
Is that a quantum boolean?
-
This post did not contain any content.
And what if it's
undefined? -
That's good to know. Don't know how I didn't know this. Been writing JS since 2000. Always just used them I guess. Ecmascripts look funny to me without them
wrote last edited by [email protected]Fair enough, I like it better without but I don't have a strong preference and have no issue adapting to whatever the style of the repo is.
I learned about it researching tools to automatically enforce formatting style and came across StandardJS, which eliminates them by default.
-
Hmm, a webdev colleague said he'd normally prefer without semicolons, but used them anyways for better compile errors.
Interesting, I'm not aware of any way they would affect compile errors. I'd be curious to know more.
-
tristate as in three states or tristate as in five states?
wrote last edited by [email protected]That is the jankiest thing I have seen in at least ten years.
Edit: because of course it's office.
-
Fair enough, I like it better without but I don't have a strong preference and have no issue adapting to whatever the style of the repo is.
I learned about it researching tools to automatically enforce formatting style and came across StandardJS, which eliminates them by default.
I can see the benefit of matching style when working with others. I only code for myself and never had to worry about conformity for project consistency.
It is good to learn new things.
I'm sure I have some coding habitats that would annoy others.
-
FILE_NOT_FOUND is from an old story on thedailywtf.com. Someone created a boolean enum with TRUE, FALSE and FILE_NOT_FOUND, if I recall correctly. It's been a recurring running joke.
thank you for letting me in on the joke
and for catching my error!
-
I can see the benefit of matching style when working with others. I only code for myself and never had to worry about conformity for project consistency.
It is good to learn new things.
I'm sure I have some coding habitats that would annoy others.
Consistent styling helps make the actual meaningful changes easier to spot. Probably also useful for your own commit history when working solo in a repo, but most useful in a team, yeah!
-
Interesting, I'm not aware of any way they would affect compile errors. I'd be curious to know more.
I don't have experience with how it affects JavaScript specifically, but independent of programming language, it usually removes the guesswork where the error might be.
The thing is that compilers use fairly static rules for their grammar. So, even if you just typo a comma where there should've been a dot, then its grammar rules don't match anymore and it doesn't really know what to do with your code.
To some degree, it's possible to say certain symbols just cannot appear in a specific place, but especially with a comma, it could be the start of the next element in a list, for example.Without semicolons, it's likely going to tell you that something's wrong between somewhere before your typo and the next closing brace (
}). With semicolons, it can generally pinpoint the specific statement where the comma is wrong.
This should also make analysis quicker while you're editing the code, as it only has to check one statement (or two, if you're inserting a new line and haven't typed the semicolon yet). -
And what if it's
undefined?root access
-
thank you for letting me in on the joke
and for catching my error!
Welcome! I guess this is your Ten Thousand moment for a mediocre joke for old programmers.
-
Ah, the ol' tristate boolean switcheroo
Classic checkbox values
-
Classic checkbox values
Yup. Checked, unchecked, and not checked.
-
Welcome! I guess this is your Ten Thousand moment for a mediocre joke for old programmers.
haha, yes - exactly! At least I got that reference, xkcd is pretty well known, though.
-
haha, yes - exactly! At least I got that reference, xkcd is pretty well known, though.
I see that they've gone back to the name "The Daily WTF". For some time, they changed to "Worse than failure" in order to avoid not even the word "fuck".
-
I don’t really follow you there, wouldn’t it be exactly the opposite and wouldn’t checking for nulls be, as a premise, more wasteful? But doesn’t really matter, time to digress. I’m conventionally educated as an engineer so what I know and find reasonable today might be outdated and too strict for most contemporary stuff.
Let's say you have a website receiving 1 million requests per day. 0.01% of those are admin requests that need to know if your are an admin to execute them. It would be wasteful to check with the database if you are an admin for every request, when only a tiny minority of then needs to know that. So for 999.900 of the requests
isAdminwill benull. We don't know if the user is an admin and we don't need to know.
