- 69
- 96 357
Manfred Steyer
เข้าร่วมเมื่อ 24 ก.ค. 2012
Interviews und Vorträge zum Thema Angular und Frontend Architekturen.
[EN] 3 Rules for Successfully Using Signals in Angular
[EN] 3 Rules for Successfully Using Signals in Angular
มุมมอง: 1 655
วีดีโอ
Let's go Zoneless - Matthieu Rieger at Angular Graz, Summer 2024
มุมมอง 600หลายเดือนก่อน
Let's go Zoneless - Matthieu Rieger at Angular Graz, Summer 2024
The state of change detection in v17, Matthieu Riegler
มุมมอง 1.6K7 หลายเดือนก่อน
Change detection is one of the core features of every framework. This feature is responsible for updating the DOM when the state of the app changes. Most of the time, change detection is a performance-sensitive matter, and knowing in detail how it works will help you get the best out of it. With the rise of Signals and recent work toward the official support of Zone-less apps, let's have a look...
Angular Best Practices, Sam Vloeberghs
มุมมอง 3.1K7 หลายเดือนก่อน
Angular has come a long way since its inception and the release of v2 a little over 7 years ago, in 2016! Best practices were part of the framework's core from the start and have evolved over time. Let's explore the best practices that are promoted from inside the framework today. Let's learn how they can ease the work for developers in creating and maintaining secure, accessible, and performan...
NgRx SignalStore: In-Depth Look at Signal-Based State Management in Angular by Marko Stanimirović
มุมมอง 6K8 หลายเดือนก่อน
NgRx SignalStore: In-Depth Look at Signal-Based State Management in Angular by Marko Stanimirović
![[EN] Meetup: The Future of Module Federation](/img/n.gif)
[EN] Meetup: The Future of Module Federation
มุมมอง 2.1Kปีที่แล้ว
[EN] Meetup: The Future of Module Federation
Sustainable Angular Architectures With Strategic Design and Nx @AngularMittelfranken
มุมมอง 5904 ปีที่แล้ว
Sustainable Angular Architectures With Strategic Design and Nx @AngularMittelfranken
Nice!!
Don’t tell my wife but I seriously love you man! Haha thank you for the content and information
Ok this was one of the best talks i have ever listened to. Will tell my coworkers about implementing an BFF
Angular Security Workshop with Philippe De Ryck: www.angulararchitects.io/en/training/angular-security-with-dr-de-ryck/
Sounds like signals are always a state of data, and it is not possible to make a decision for invoking data change based on data state, the concept of `view = function(state)` is broken in such case. Data could not have an intention to be self changed (via `effect`), because behaviour is not a data or state feature. Behaviour that based on Action/Event is a missing part of signal architecture
We're here in Styria -> we're distilling everything 🤣🤣🤣
Nice talk as always.
first time I see the injections with # prefix. Is there a convention on why did you write it like that?
Not really. It’s the official ecmascript syntax (es2022) and I decided to use it in this example. Saying this, the TypeScript private also has several benefits: it’s easier to debug (because it’s actually public after transpiling to JavaScript) and it comes with no performance overhead at runtime (for the same reason).
@@ManfredSteyer Thanks for clarification :)
This was great. Love signals, but having to use untracked() heavily lol
I totally feel you. Using untracked or some wrapper around it like a custom explicitEffects helper or toObservable really helps to see what’s going on and to avoid issues.
awesome . thank you for sharing
Angular Architecture Workshop: www.angulararchitects.io/en/training/advanced-angular-architecture-workshop/
Great stuff!
That being said, the innnovation section at 7:20 is close to perfect, things are moving in the right direction
Do not add signals
Signals is the best thing that ever happened. What are you talking about ? ALL frameworks are moving (or have moved) to signals, and that is with a good reason. Fine grained change detection is amazing. Ditching zoneJS is amazing. I can't imagine not using signals by now.
@@LarsRyeJeppesen Signals are not the best thing and should not be used for everything. The second you need some asynchronous data it becomes a hassle with computed -> toObservable -> toSignal etc. They solve a tiny thing but people misuse them already.
Bad bad bad , a lot of changes and angular is becoming unpopular
Jesus lord, I hope for the love of God they don't waste their resources on AI
IMHO, there is a lot of potential for using AI for migration scripts, as LLMs are pretty good with source code.
@@ManfredSteyer LLMs are just a hit or miss when it comes to code, I have yet to find a task of mine that has been taken over by AI code generators, that's if you're a senior of course.
@@hendrx Absolutely agree. It's a productivity boost in some cases.. It's a stack-overflow on steroids.
@@LarsRyeJeppesen it's a code snippet generator at this point
Thanks for sharing, looking forward to going zoneless in our next project!
We did and it is awesome
Thankyou, This looks brilliant! I too really am a fan of the original global store, and redux pattern, and the devtools. When using the other stores, such as component store, I essential thing I really missed was the the devtools, as they have been a life saver to me in the past when debugging and tracking what actions change the state. This would be worth it just for the devtools, but now also with this redux pattern as well, this will really could convince me to swap from the global store over to the signal store.
wie ist das mit dem Feature withDevTools in production Mode... ich muss den Toolkit ja unter "dependencies": { installieren, weil ich ja evtl. withcallState verwenden möchte. In Produktion möchte ich aber nicht die Devtools sehen ?
Hast recht. Es gibt da eine schnelle und eine etwas längere Lösung. Die schnelle ist ein Flag, wo du es während der Produktion nicht läuft, aber das JavaScript trotzdem im Bundle ist. Die lange ist, dass es auch aus dem Bundle fliegt. Das wird ein bisschen knackiger. Kannst du fürs erste Mal mit der schnellen Lösung leben? Installieren musst das toolkit natürlich in dependences (hast eh schon erklärt wieso).
@@RainerHahnekamp Hi Rainer :-) super danke für die schnelle Antwort... das Flag muss ich dann selber in meinen Store einbauen? oder gibt es das irgendwo ? liebe Grüsse :-)
@@koempf Serwas, nein das gibts noch nicht. Das müsste ich noch machen. Wäre super, wenn du mir einen Issue auf GitHub anlegen könntest. Dann hab ich einen offiziellen "Arbeitsauftrag". Falls nicht, kanns aber ich auch so machen.
@@RainerHahnekamp super ich mache einen Eintrag :-) noch kurz eine letzte Frage :-) bei der standalone patchState function... da muss ich bei Objekten immer die immutability beachten ? ich wurde da bei einem internen Vortrag gefragt ob es dafür eine Library gibt um das nicht immer machen zu müssen 🙂
@@koempf ja, gibts: github.com/timdeschryver/ngrx-immer. Wir werdens aber auch im toolkit irgendwann aufnehmen.
4th Option: Jasmine/Jest for everything with @puppeteer/ng-schematics
a train, that is too fast. 🙂. In germany this will never happen.
The summary of our Dev conclusions. Thanks.
51:21 Servus, is there a reference to the Playwright initiative so we can see what has happened with it?
Please!! Could you make a video or a course explaining how to test AngularFire within a standalone app? like firebase authentication or firestore?. Thank you
This was great. Reminds me to implement webauthn on our internal site.
Angular Architecture Workshop: www.angulararchitects.io/training/advanced-angular-architektur-workshop/
Here is the link to my slides: speakerdeck.com/rainerhahnekamp/towards-modern-change-detection
Seems like my hair was a bit excited at the beginning 😀
Source code at github a at: boudard/springboot-module-federation
Source Code provided by Alain: github.com/aboudard/springboot-module-federation
I'd love to be able to post the url of the repo, but my comments keep being deleted.
Seems like it worked now. Please see my comment outside of this thread.
Is there a code repo for this?
The interviews are good, but without having reference source code to read and follow, these are of no interest to me.
@@AaronScribner-qj5qs he points to his github at aboudard for the angular-module-federation project
Thanks a million Manfred for having me ! It was a pleasure to share with you !
Angular Architecture Workshop: [English] www.angulararchitects.io/en/training/advanced-angular-architecture-workshop/ [German] www.angulararchitects.io/training/advanced-angular-architektur-workshop/
Angular Renaissance 🚦
Am using Angular 18 next 5 with the zoneless changedetector, so far working like a charm. Super exciting.
Awesome stuff
Modern Angular Workshop www.angulararchitects.io/en/training/modern-angular-workshop/
sensational stuff
Great stuff, thanks. Excited for what is coming
Great talk, lot of insights around test development
Thanks, nice to hear!
Great talk.
Thanks!
Awesome video Manfred and Rainer! I think this is a perfect follow-up to Alex's GitHub comment in February about TestBed/effects. I've been a proponent of skipping TestBed for unit tests, but I've come around to the "Testing Trophy" model focusing on component tests, particularly using Playwright. I still prefer to skip TestBed for Services and Pipes though just to help keep things simple.
Very informative, thanks
You are welcome Lars!
Danke euch viel mal für den wirklich sehr informatieven Beitrag.
Danke auch!
Workshop: Professional Angular Testing -- Playwright Edition www.angulararchitects.io/en/training/professional-angular-testing-playwright-edition/
Workshop: Professional Angular Testing: Playwright Edition www.angulararchitects.io/training/professional-angular-testing-playwright-edition/
What kind of approach was used to share state between angular shell and react mfe?
@alejandroramirezjimenez757 Great Insight. Curious to know, how does web components and module federation works togather?