Python type hints may not be not for me in practice

Re:Python type hints may not be not for me in practice by josephg on Thursday November 28, 2024 @04:30AM (#42263875)

Sounds like a bug in the type definitions. Thats an unfortunate consequence of typescript being glued to javascript: If you import a package that is authored in javascript, there's no guarantee that the type definitions are written correctly or kept up to date. Sometimes they don't exist at all.

It doesn't happen too often, but its definitely annoying.

In cases like this, the easiest way is to just add as any to your expression - which essentially turns off type checking for that expression. Maybe that's what you did?

    fetch('foo.json', {...} as any)

I don't think there's anything wrong with this. Using typescript types for only 95% of your code rather than 100% still provides a lot of value in my opinion.

You can also ctrl+click on functions like this and read the actual types they're expecting.

[ Parent | on HN ]

Re:Python type hints may not be not for me in practice by pmontra on Thursday November 28, 2024 @05:51AM (#42264271)

I did this:

  const response = await fetch(
    url,
    {
      method: 'POST',
      headers: {
        'Content-Type': 'application/json',
      },
      body: JSON.stringify(reqData),
    }
  );
  const resData: ApiResponse = await response.json();

then I parsed resData. The JSON in the response is still type checked but I don't have to fight anymore with the HTTP library. I can't remember what it was as it never made it into a commit.

[ Parent | on HN ]

Re:Python type hints may not be not for me in practice by josephg on Thursday November 28, 2024 @05:56AM (#42264316)

Yeah makes sense. Now that fetch is standardized and built in to node, frankly I don't see any reason to ever pull in request.

[ Parent | on HN ]