magbeat

joined 2 years ago
sorted by: new top controversial old
1
Angular 18 is out (blog.angular.dev)
1
Introduction to @let in Angular 18 - by Rodrigo Oler (dev.to)
submitted 11 months ago* (last edited 11 months ago) by magbeat@programming.dev to c/angular@programming.dev
0 comments fedilink
1
Adding fallback content for ng-content (dev.to)
 

Adding fallback content for ng-content got a lot easier with Angular v18

1
Web Test Runner to replace Karma? (www.danywalls.com)
 

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.

1
Very nice and complete article how to create a signal component in modern Angular (blog.angular-university.io)
1
Transform Inputs Properties in Angular Easy (dev.to)
 

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.

1
Simple Unsaved Data Changes Guard in Angular 17+ (medium.com)
1
Angular v17 is ready (github.com)
 

Angular v17 is ready 🥳

https://github.com/angular/angular/releases/tag/17.0.0

and:

https://www.npmjs.com/package/@angular/core

#angular @angular@a.gup.pe

1
Stop, don’t use ActivatedRoute anymore to get your route data! (medium.com)
 

Never heard and never used this feature of Angular v16.

1
Episode 23/43: Angular Love Meetup, Younes Jaaidi on Testing (medium.com)
 

Has anyone already switched to Jest? Has anyone already gained experience with Playwright Component Tests in Angular?

1
The state of Change Detection in Angular v17 (riegler.fr)
1
Angular’s Improved Tooling: Standalone Migration Magic (blog.herodevs.com)
submitted 2 years ago* (last edited 2 years ago) by magbeat@programming.dev to c/angular@programming.dev
0 comments fedilink
 

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.

Configuration Asp.NetCore in c/csharp@programming.dev
[–] magbeat@programming.dev 7 points 2 years ago

As @nibblebit@programming.dev 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

view more: next ›