magbeat @programming.dev Software Engineer (#dotnet, #angular, #flutter, #typescript, #dart, #golang, #docker, #kubernetes), very interested in Software Architecture and Methodology (#ddd, #tdd, #cleancode, #agile), proud father of two girls and drummer and Linux (Fedora) user
https://novaloop.social/@magbeat
Introduction to @let in Angular 18 - by Rodrigo Oler
Angular 18 has brought an exciting new feature for developers: the `@let` directive. This tool helps you create variables quickly and easily within HTML code. Let’s understand how it works and look at some cool examples.
- by Rodrigo Oler
Adding fallback content for ng-content
Angular v18 recently introduced a new feature to easily define a fallback content in ng-content...
Adding fallback content for ng-content got a lot easier with Angular v18
Web Test Runner to replace Karma?
Explore the shift from Karma to Web Test Runner for Angular testing, highlighting its experimental integration and future potential
Was waiting for a long time for jest to replace karma. It seems there is a new test runner overtaking jest for Angular testing: Web Test Runner.
Very nice and complete article how to create a signal component in modern Angular
A complete guide to Angular signal components, the new component authoring format. This includes signal-based inputs, outputs, and two-way binding with model().
When you are developing a UI library (as we are) we want to support the old API for some time and mark is a deprecated. So one would add a second @Input() of type ScheduleEvent[] leave the old API be as Course[] and mark it as deprecated. In the next major version you could then retire the old API.
When building components, defining the interfaces to be used by consumers is often challenging. We...
Great usecase for the transforming @Input properties.
We will have to refactor a huge (and I mean huge) component for a customer in the near future. The consuming teams should not notice any of this. transform could be very useful for this.
Angular v17 is ready
17.0.0 (2023-11-08) Commit Description remove support for Node.js v16 (#51755) animations Commit Description Add the possibility of lazy loading animations code. (#50738) rem...
Angular v17 is ready 🥳
https://github.com/angular/angular/releases/tag/17.0.0
and:
https://www.npmjs.com/package/@angular/core
#angular @[email protected]
Stop, don’t use ActivatedRoute anymore to get your route data!
Never heard and never used this feature of Angular v16.
Episode 23/43: Angular Love Meetup, Younes Jaaidi on Testing
Has anyone already switched to Jest? Has anyone already gained experience with Playwright Component Tests in Angular?
Angular’s Improved Tooling: Standalone Migration Magic
Nice article on how to use the Angular Schematics to convert a project to all standalone components and about what the schematics actually do in every step.
Local Change Detection for Components using Signals
This commit updates the reactive template and host binding consumers to only mark their declaration components for refresh, but not parents/ancestors. This also updates the AfterViewChecked hook to...
Angular will not mark all parents of a component as dirty if the component uses signals in the template.
Angular Toward Its Renaissance🚀✨ (Medium Members only!)
Very nice overview on what's new and why it is good from Angular v14 - v17
Unfortunately it is "member-only" on medium.
Good thread about Dotnet people on Mastodon
Angular Community in the Fediverse
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?
Angular 17 - next-4 release
17.0.0-next.4 (2023-09-13) core Commit Description support styles and styleUrl as strings (#51715) router Commit Description Add feature to support the View Transitions API (#51314)
Small release, but quicker cycle now.
Yes, you are right. Long living branches are the problem.
In this case it is a completely new project in the workspace (of course depends on the library in the workspace). It is a POC that has been postponed again and again by the customer due to priorities.
I think it's probably best to isolate the branch and take it out of the workspace. When it is ready, we can integrate it back into the workspace.
As @[email protected] said you can use multiple configuration providers. We usually have local appsettings.json files, even per machine appsettings.<HOSTNAME>.json and then use Environment Variables that are stored in a vault for the production environment. We add the appsettings.<HOSTNAME>.json files to .gitignore so that they don't get checked in.
var env = Environment.GetEnvironmentVariable("ASPNETCORE_ENVIRONMENT");
configuration.AddJsonFile($"appsettings.{env}.json", optional: true, reloadOnChange: true);
configuration.AddJsonFile($"appsettings.{Environment.MachineName}.json", optional: true, reloadOnChange: true);
configuration.AddEnvironmentVariables();
Then you can provide the secrets as environment variables in the form of DATA__ConnectionString