inferred vs generated TypeScript types: how Payload CMS decided

แชร์
ฝัง
  • เผยแพร่เมื่อ 13 ต.ค. 2024

ความคิดเห็น • 10

  • @neilballer6600
    @neilballer6600 ปีที่แล้ว

    And now I understand why the declare module empty object exists. Incredible work Payload! I am wowing daily.

    • @MichiganTypeScript
      @MichiganTypeScript  ปีที่แล้ว +1

      of course, we're pretty biased, but Payload sure seems to have some pretty great leadership.

    • @neilballer6600
      @neilballer6600 ปีที่แล้ว

      @@MichiganTypeScript understandably so. Regardless of geography, James and the crew are on to something huge. Unofficial fanboy here for a few months now.

  • @kasper_573
    @kasper_573 ปีที่แล้ว

    I really hope type inference becomes more performant. I use it for everything nowdays. Fully typesafe full stack monorepo with zero codegen is doable today, but it really slows down the editor .

    • @MichiganTypeScript
      @MichiganTypeScript  ปีที่แล้ว

      indeed! it's hard to say what will happen but it sure does _seem_ like there's a LOT more attention being paid to TypeScript performance these days!

  • @medbenbrahim3246
    @medbenbrahim3246 10 หลายเดือนก่อน

    I feel like the typescript file could become actually the source of truth, instead of having a JSON config, use a typescript file to define the schema.
    TS annotations could be a solution, to add your own DSL info

    • @MichiganTypeScript
      @MichiganTypeScript  10 หลายเดือนก่อน

      maybe over time things will settle into something like this. One of the things holding a lot of places back from doing this is that there's no formal specification for TypeScript's types. This makes the people who sign on the dotted line nervous.

  • @jjo954
    @jjo954 ปีที่แล้ว

    Thanks a lot!

    • @MichiganTypeScript
      @MichiganTypeScript  ปีที่แล้ว

      of course! what did you like? what kinds of things would you like to see more of?