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
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
Just a very minor note: I'd keep the model directory without the plural form. Rationale: When talking about the source code of a program, we also typically refer to multiple source files. Still, it is not called source codes. The singular is appropriate here as an unmarked form.
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:
model
folder would need to change tomodels
models
folder (f. ex.xml
) conversions into other formats could be done via github actions and stored either in subfolders (within themodels
folder) or different folders in the repository (f.ex. a folder calledjson
for alljson
models etc.)memote report diff
would be preferable over reports for every modelCurrent feature/value/output:
Not available.
I hereby confirm that I have:
main
branch of the repositoryThe text was updated successfully, but these errors were encountered: