
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
Angular 18 is out
2y 5d ago in angular@programming.dev from blog.angular.devIntroduction to let in Angular 18 - by Rodrigo Oler
2y 7d ago in angular@programming.dev from dev.toAdding fallback content for ng-content
Web Test Runner to replace Karma?
2y 1mon ago in angular@programming.dev from www.danywalls.comVery nice and complete article how to create a signal component in modern Angular
Transform Inputs Properties in Angular Easy
2y 7mon ago in angular@programming.dev from dev.toWhen 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.
Simple Unsaved Data Changes Guard in Angular 17+
2y 7mon ago in angular@programming.dev from medium.comAngular v17 is ready
2y 7mon ago in angular@programming.dev from github.comStop, don’t use ActivatedRoute anymore to get your route data!
2y 7mon ago in angular@programming.dev from medium.comEpisode 23/43: Angular Love Meetup, Younes Jaaidi on Testing
2y 7mon ago in angular@programming.dev from medium.comAngular Community in the Fediverse
2y 9mon ago in angular@programming.devGood thread about Dotnet people on Mastodon
Out of sync branches in a Angular Workspace
2y 9mon ago in angular@programming.devYes, 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.
Configuration Asp.NetCore
2y 11mon ago in csharp@programming.devAs @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







