Description of the issue:
So far only singular GEM repositories fit within the standard-GEM template. While some parts can easily be used with multiple GEMs, such as the overall structure, other things fall short when multiple GEMs are hosted in one repository.
Expected feature/value/output:
There are two ways how to approach this:
- One could either extend this repository to be applicable to repositories with multiple GEMs
- Or create a separate template for multiple-GEM-repositories
A few changes that directly came to my mind are:
- the
model folder would need to change to models
- one model format should be stored in the
models folder (f. ex. xml) conversions into other formats could be done via github actions and stored either in subfolders (within the models folder) or different folders in the repository (f.ex. a folder called json for all json models etc.)
- the naming convention for the GEMs needs to be adapted
- as a possible Memote report, a
memote report diff would be preferable over reports for every model
Current feature/value/output:
Not available.
I hereby confirm that I have:
Description of the issue:
So far only singular GEM repositories fit within the standard-GEM template. While some parts can easily be used with multiple GEMs, such as the overall structure, other things fall short when multiple GEMs are hosted in one repository.
Expected feature/value/output:
There are two ways how to approach this:
A few changes that directly came to my mind are:
modelfolder would need to change tomodelsmodelsfolder (f. ex.xml) conversions into other formats could be done via github actions and stored either in subfolders (within themodelsfolder) or different folders in the repository (f.ex. a folder calledjsonfor alljsonmodels etc.)memote report diffwould be preferable over reports for every modelCurrent feature/value/output:
Not available.
I hereby confirm that I have:
mainbranch of the repository