this post was submitted on 29 Aug 2023
5 points (100.0% liked)

Angular

277 readers
8 users here now

A community for discussion about angular

Wormhole

[email protected]

Logo base by Angular under CC BY 4.0 with modifications to add a gradient and drop shadow

founded 1 year ago
MODERATORS
 

Hi there

I have a question about Angular workspaces:

We sometimes have long living branches next to develop. Now, if a team runs the schematics migrations from a library and update their code, it's possible that a different team (on a different branch) has new features that aren't updated by the schematics (because the new feature code obviously is not there).

Has anyone already had the same problem and found a solution?

you are viewing a single comment's thread
view the rest of the comments
[–] magbeat 1 points 1 year ago

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.