magbeat
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
- 22 Posts
- 3 Comments
Joined 1 year ago
Cake day: June 30th, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
Good thread about Dotnet people on Mastodon
1·1 year agoYes, 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.
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 typeScheduleEvent[]leave the old API be asCourse[]and mark it as deprecated. In the next major version you could then retire the old API.