Been working on the showcase project I will be showing longer than I knew I would be showing it anywhere. Looking forward to being on the stream again.
#Angular 22 is coming! A lot of exciting things are happening, and one of them is having @MichaelSmallDev on!
The very first guest of our streams is back to help us navigate through what changes the new Angular version brings, so tune in tomorrow at 4:30 PM UTC!
Thank you everybody for joining us! If you want to see two repositories that I made for demos (v22 overview and signal forms experimenting), I have included them and other links in a gist: https://t.co/yV14z0sr5J
Just one hour left! Join me and @MichaelSmallDev as we explore #Angular 22 and see what exciting new things are about to drop!
Link to watch on YouTube ⬇️
Just one hour left! Join me and @MichaelSmallDev as we explore #Angular 22 and see what exciting new things are about to drop!
Link to watch on YouTube ⬇️
@codeofarmz@angular I think so, I find that the ability for jetbrains's language service to detect that is a major bonus for it. I assume that is what you are using to see this warning, but just giving context for people who don't.
We have talked about ngxtension, one of the lightweight yet powerful #Angular libraries on different occasions, and even had two of the core contributors!
But I realized we never dedicated a specific episode to exploring this fantastic open source project.
So, this Wednesday, March 18th, 4:30 PM UTC, let's correct this oversight and finally have a deepo discussion about ngxtension!
⚠️ New #Angular XSS
💡 XSS in i18n attribute bindings
A high-severity XSS security issue affecting i18n attribute bindings has been identified in Angular.
@nagababu_korada@angular I miss when the Nx VSC plugin worked for Angular CLI projects, I liked how it ran dryruns as you tested configurations in the GUI.
@shinobicode_dev@angular The prebuilt component commands are definitely something I always forget about, despite them being a good CLI boilerplate handler. I wonder what kind of stuff libraries could do with that... or even if I made an internal package for work with a generator.
@synalx@the_h0bbyte@Jean__Meche@ipwanciu https://t.co/1oIuV1aroW
I haven't used it in practice because normally I can compute something in a different way. But I have seen variants of this pop up enough that ngxtension has had this most of the time now.
@SergeyGultyayev@synalx@Jean__Meche@ipwanciu I reviewed a PR recently where the AI tried to return a computed from a function. Doing so seemed to invalidate the benefits of the computed as it fired off more computations than if it was a normal computed value. Ended up refactoring to a computed that was iterated over.
@NateDevelops Well well well, ngxtension just reading our minds lol. ngxtension's signals for routes already so good, but this is even better.
https://t.co/xAYhTVsx4O
https://t.co/GPPLN5UHL0
NgRx Toolkit v21
- About the Toolkit
- v20 minor features (with[Entity]Resource/Mutations)
- v21 features (event devtools, resource error handle, `clearUndoRedo` in favor of `store.clearStack`)
- Backports
Thank you to our contributors and users alike!
https://t.co/705wV5BiXv
@zoaibdev https://t.co/QZzCLzXxEo they are waiting for resource to go beyond experimental. Not sure if that means developer preview will be the moment or if they would wait for it to be marked stable. But there is also a couple things to be ironed out in withResource still as well.