NgRx SignalStore: In-Depth Look at Signal-Based State Management in Angular by Marko Stanimirović

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

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

  • @AsGoodAsItGets78
    @AsGoodAsItGets78 11 หลายเดือนก่อน +1

    Terrific presentation Marko, thank you!

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

    Great video. It would be interesting to see how this examples are tested, though e.g. the Counter Component and the CounterStore.

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

    And is there something planned regarding the management of suspense states, hence having information regarding loading and error states out of the box? Could something like this be easily built using custom features?

    • @PlerbyMcFlerb
      @PlerbyMcFlerb 9 หลายเดือนก่อน

      I have the same question. Wondering if there's a way we can defer initialization and hand the signal store an initial state. Otherwise I'd end up with optional properties everywhere which feels wrong.

  • @g3co875
    @g3co875 11 หลายเดือนก่อน +1

    thanks!

  • @rockenOne
    @rockenOne 8 หลายเดือนก่อน

    sensational stuff

  • @emberarc
    @emberarc 10 วันที่ผ่านมา

    But we definitely don't want to define dynamic class properties or methods. That's why we use a typed language like TS.

    • @ManfredSteyer
      @ManfredSteyer  10 วันที่ผ่านมา

      I might look like dynamic props at first glance. But it's indeed statically typed. The NGRX does a great job telling TypeScript about the Types of all the props you define.

  • @emberarc
    @emberarc 10 วันที่ผ่านมา

    Since the appearance of signals, I feel like the Angular dev team, following the waves of trends, is turning a well-thought-out enterprise-level framework into something React-like and FP-oriented. Big mistake.

  • @mayori-engineering-hub
    @mayori-engineering-hub 10 หลายเดือนก่อน +2

    It does not make sense .. signal needs to be more mature.. but thanks for the presentation