You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently in Labs, deployable project heads for individual components and the "all components" project are hardcoded.
For individual components, these projects heads are in each component. For the "All" solution, these heads are in the ./platforms repo folder.
The problem
Making changes to these projects so far has been a long and manual process. Even simple changes require changes to potentially hundreds of files. Scripting these migrations is not an option as it's cumbersome and error prone.
The solution
Find a way to generate project heads from a template in the ./common folder. This folder will be migrated to a submodule later. By having the user generate these first, it allows us to effectively update all heads via the submodule.
Implementing this means the user needs to generate the project heads before opening the solution file. We should close this off alongside #257 if possible.
The text was updated successfully, but these errors were encountered:
Background
Currently in Labs, deployable project heads for individual components and the "all components" project are hardcoded.
For individual components, these projects heads are in each component. For the "All" solution, these heads are in the
./platforms
repo folder.The problem
Making changes to these projects so far has been a long and manual process. Even simple changes require changes to potentially hundreds of files. Scripting these migrations is not an option as it's cumbersome and error prone.
The solution
Find a way to generate project heads from a template in the
./common
folder. This folder will be migrated to a submodule later. By having the user generate these first, it allows us to effectively update all heads via the submodule.Implementing this means the user needs to generate the project heads before opening the solution file. We should close this off alongside #257 if possible.
The text was updated successfully, but these errors were encountered: