1
Angular 18 is out (blog.angular.dev)
1
submitted 2 years ago* (last edited 2 years ago) by magbeat@programming.dev to c/angular@programming.dev
1

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

1

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
1

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
1
1

Never heard and never used this feature of Angular v16.

1

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

1
1
submitted 2 years ago* (last edited 2 years ago) by magbeat@programming.dev to c/angular@programming.dev

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.

[-] magbeat@programming.dev 6 points 3 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 ›

magbeat

0 post score
0 comment score
joined 3 years ago