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
I have verified this is the correct repository for opening this issue.
I have verified no other issues exist related to my request.
Is Your Feature Request Related To A Problem? Please describe.
There have been a number of issues around remembered arguments (#1443, #2111, #2752, #2886, #2761), which largely have been around how the remembered argument are saved, specifically with how they have to be parsed back into the configuration.
Describe The Solution. Why is it needed?
So it might be a good idea to not save command line arguments, but instead serialize an object to a file. So for example an xml file with the package parameters, install arguments, etc as elements. This allows for more flexibility in parsing the file later, and more options for mapping the resulting object to the current configuration. It also avoids having to go through a command line argument parser.
Checklist
Is Your Feature Request Related To A Problem? Please describe.
There have been a number of issues around remembered arguments (#1443, #2111, #2752, #2886, #2761), which largely have been around how the remembered argument are saved, specifically with how they have to be parsed back into the configuration.
Describe The Solution. Why is it needed?
So it might be a good idea to not save command line arguments, but instead serialize an object to a file. So for example an xml file with the package parameters, install arguments, etc as elements. This allows for more flexibility in parsing the file later, and more options for mapping the resulting object to the current configuration. It also avoids having to go through a command line argument parser.
Additional Context
I have a prototype of how this might work here: https://github.com/TheCakeIsNaOH/choco/tree/remembered-args-xml
The implementation has similarities to the changes in #3003
Related Issues
No response
The text was updated successfully, but these errors were encountered: