Is your feature request related to a problem? Please describe.
When students work on different subsystems, they make independent changes to the elastic layout that is saved as one .json file. Because of this file's structure, these often leads to hard-to-resolve merge conflicts when integrating those branches together, particularly for our tuning layout that includes tabs for each subsystem. JSON is generally difficult to merge.
Describe the solution you'd like
If there were a way to compose a layout using an include directive, that may reduce the number of conflicts, e.g.
"tabs": [
{
"include": "shooter_tuning.json"
}, ...Describe alternatives you've considered
The alternative is to have multiple, separate layouts saved in different files. But then only one could be active at a time.
Additional context
Noticed this during development.
Is your feature request related to a problem? Please describe.
When students work on different subsystems, they make independent changes to the elastic layout that is saved as one .json file. Because of this file's structure, these often leads to hard-to-resolve merge conflicts when integrating those branches together, particularly for our tuning layout that includes tabs for each subsystem. JSON is generally difficult to merge.
Describe the solution you'd like
If there were a way to compose a layout using an
includedirective, that may reduce the number of conflicts, e.g.Describe alternatives you've considered
The alternative is to have multiple, separate layouts saved in different files. But then only one could be active at a time.
Additional context
Noticed this during development.