overview for magbeat

4

Local Change Detection for Components using Signals (github.com)

submitted 2 years ago by magbeat to c/angular

0 comments fedilink

Angular will not mark all parents of a component as dirty if the component uses signals in the template.

-3

Angular Toward Its Renaissance🚀✨ (Medium Members only!) (famzil.medium.com)

submitted 2 years ago* (last edited 2 years ago) by magbeat to c/angular

0 comments fedilink

Very nice overview on what's new and why it is good from Angular v14 - v17

Unfortunately it is "member-only" on medium.

0

Updates from the Angular Team | Mark Thompson & Alex Rickabaugh (www.youtube.com)

submitted 2 years ago* (last edited 2 years ago) by magbeat to c/angular

0 comments fedilink

2

Very nice explanation of a new Angular 17 Feature: Deferrable Views and Deferred Loading in Templates (www.youtube.com)

submitted 2 years ago by magbeat to c/angular

0 comments fedilink

0

Special Angular Event (6th November 2023) (www.youtube.com)

submitted 2 years ago by magbeat to c/angular

0 comments fedilink

4

CSS-Only Scroll-Driven Animation and Other Impossible Things (youtu.be)

submitted 2 years ago by magbeat to c/angular

0 comments fedilink

8

Angular Community in the Fediverse (self.angular)

submitted 2 years ago by magbeat to c/angular

5 comments fedilink

I am a full-stack developer and for the backend we use Dotnet. A lot of the Dotnet developers have made the switch to the fediverse.

But I miss good Angular content over here. The people I followed on Twitter are pretty much still there and have not switched over.

What do you think about that? Do you have any recommendations for people to follow on Mastodon?

2

Angular 17 - next-4 release (github.com)

submitted 2 years ago by magbeat to c/angular

0 comments fedilink

Small release, but quicker cycle now.

5

Angular 17 - next-3 released (github.com)

submitted 2 years ago by magbeat to c/angular

0 comments fedilink

5

Out of sync branches in a Angular Workspace (self.angular)

submitted 2 years ago by magbeat to c/angular

2 comments fedilink

Hi there

I have a question about Angular workspaces:

We sometimes have long living branches next to develop. Now, if a team runs the schematics migrations from a library and update their code, it's possible that a different team (on a different branch) has new features that aren't updated by the schematics (because the new feature code obviously is not there).

Has anyone already had the same problem and found a solution?