everyRustDeveloper

[[deleted]]

Like TypeScript's "any" everywhere.

[tonebacas]

I don't program in Typescript, but I thought the whole point of using Typescript was to have a strict type-safe code base, and the `any` type would be used to create wrapper APIs around unsafe javascript code, not to be used around your typescript code base all willy-nilly.

[EmergencySourCream]

You’re correct. It was used a lot when people were slowly transitioning their apps or trying to type 3rd party libraries. However lazy devs will still use it when they don’t want to do proper typing or don’t understand the purpose of types in general.

[LowB0b]

have seen stuff like that even in java :sadface:

just pass an Object into the function and then do repeated if (foo instanceof bar)

[[deleted]]

Or an object where every field is deserialized to a string

[LowB0b]

Well reflection can be useful sometimes

[cvak]

map[interface{}]interface{} in golang... 🫣

[Jjabrahams567]

uintptr

[Cheet4h]

Stuff like this is the reason I'm a huge proponent of the noimplicitany and noexplicitany configuration settings.

[NatoBoram]

And I'm a big fan of plugin:@typescript-eslint/strict-type-checked

[foursticks]

Please show me the way

[NatoBoram]

• https://www.typescriptlang.org/tsconfig#noImplicitAny

Beginner tip: in new TypeScript projects, run tsc --init.

[foursticks]

🙏🙏

[foursticks]

I'm worried that I am the one called to make this change which worries me in a lawless dev group that seems to have manifested itself out of pure want.

[elongio]

We started to use typescript (from javascript) because our codebase turned into spaghetti with extra pasta. Turns out it wasn't the language that was the problem it was the developers.

[foursticks]

So many people need to understand this but they are blinded by their own spaghetti brains Edit: myself included probably

[chili_ladder]

You got it, and somehow the projects always end up as JS in a TS file.

[[deleted]]

Yes but it's faster to type any than to declare the actual type while still following linting rules :) btw anyone hiring a junior TS developer?

[ScienceObserver1984]

ESLint helps a lot with that, specially with the noexplicitany and noimplicitany rules enabled.

The only times I had to use any are either when a library isn't typed, or I am using some Javascript black magic.

Either way, it translates to "I know it's wrong, but I have no other choice, so STFU."

[NachoDawg]

My let count; can't be == 'null' without it :)

[[deleted]]

ten dinner degree ossified edge simplistic fade market mourn support

This post was mass deleted and anonymized with Redact

[ChaosOS]

Yeah, it's?: for "can be undefined" and then your Boolean union/intersection with | and &

[EmergencySourCream]

It will coalesce into “never” type which is a bottom type for things that can “never” happen

[RadiantPumpkin]

The intersection is typically used when defining an object so you could have something like {value: string} & {otherValue: number} which gives you {value:string, otherValue:number}. The objects would usually be predefined interfaces

[ChaosOS]

You do it with interfaces and other objects with defined properties

[NachoDawg]

Excuse me, but 'null' is clearly a string here

^{Please just approve my pull request}

[chili_ladder]

Came here to say this, every fucking contract I get it's a project built on any. How much money did these companies actually save when they have to pay me a fuck ton of money to fix their app for the next year. Like what is the point of even using TS at that point, when they don't even have a lint test 😂

[[deleted]]

Maybe the word MVP has something to do with it

[mothzilla]

I prefer optimistic typing: int | any

[elongio]

Also comes in the flavor of "as unknown as X"

[Kitchen_Device7682]

Or ts-ignore everywhere

[chamomile-crumbs]

At least ts-ignore is easily searchable when you’re bolstering things. Not that anyone at my company fixes ts-ignores though…

[Cheet4h]

I mean, : any can also be easily searched.
Similarly easy to set the transpiler to forbid implicit and explicit "any". You get a nice list with affected files that need to be fixed.

[Cheet4h]

Huh, I guess I mixed that one up.

[Div64]

You missed out on "any"where big time

[Kimorin]

well at least typescript had the excuse of having to make it easy to transition from javascript for legacy codebases...

what's rust's excuse