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
Is your feature request related to a problem? Please describe.
Right now, a configuration for PROLEAD is written in a custom format and thus requires a custom parser.
Therefore, we have to maintain the code for parsing the config.
Furthermore, the structure of the config file is not straight forward.
It takes some time to get familiar with it.
Thus, it could be advantageous to use a well established file format,
which is already known by the users.
Describe the solution you'd like
It would be great to have the possibility to configure PROLEAD via a JSON or YAML config file.
This addresses both the requirement of maintaining a custom parser and using a well established file format.
Therefore, we should evaluate alternative libraries which can parse JSON or YAML.
In a next step, we should implement a new configuration parser utilizing one of the evaluated libraries.
PROLEAD is used broadly for research.
Therefore, it is necessary that we do not drop support for the old parser directly after finishing the new one.
This could cause problems with submitted artifacts.
Furthermore, a converter from the old in the new configuration file format should be provided.
Describe alternatives you've considered
Change nothing.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Right now, a configuration for PROLEAD is written in a custom format and thus requires a custom parser.
Therefore, we have to maintain the code for parsing the config.
Furthermore, the structure of the config file is not straight forward.
It takes some time to get familiar with it.
Thus, it could be advantageous to use a well established file format,
which is already known by the users.
Describe the solution you'd like
It would be great to have the possibility to configure PROLEAD via a JSON or YAML config file.
This addresses both the requirement of maintaining a custom parser and using a well established file format.
Therefore, we should evaluate alternative libraries which can parse JSON or YAML.
In a next step, we should implement a new configuration parser utilizing one of the evaluated libraries.
PROLEAD is used broadly for research.
Therefore, it is necessary that we do not drop support for the old parser directly after finishing the new one.
This could cause problems with submitted artifacts.
Furthermore, a converter from the old in the new configuration file format should be provided.
Describe alternatives you've considered
Change nothing.
The text was updated successfully, but these errors were encountered: