Skip to content

Fixing broken type definitions #50

Description

@karol-majewski
  • Your full name: Karol Majewski
  • Target audience (beginner/intermediate/advanced/everyone): everyone
  • Estimated duration: 5 minutes
  • Keywords: @types, DefinitelyTyped, patch-package, module augmentation

Fixing broken type definitions

The talk

One-sentence summary

How to deal with incorrect third-party type definitions.

What's the format — is it a case study, a live coding session, a workshop or something else?

Case study.

Tell us more about the talk

In a perfect world, every library is created with TypeScript and the provided type definitions describe the API fully.

But we don't live in a perfect world. Sometimes types are not even there. Sometimes they are incomplete. Sometimes the version of type definitions doesn't match the actual API of the library. Sometimes they are written in such a way you cannot even augment them locally.

Yet we have no choice. The library is in use and removing it from the project just because it's poorly typed is not always possible.

What can you do?

You

A few words about yourself

How can we find you on social media?

https://twitter.com/karoljmajewski

Would you be willing to have a Q/A session after the talk?

Sure.

Do you mind if we record the event?

Yes.

Is there anything we can help you with?

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions