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
It seems that this functionality can be added with minimal changes. It would be a good addition if the user could add one or more command line arguments such as: --component = 3080
or --component = RTX3080
I'm not sure if the parts would need to be on an internal list to match syntax properly. If the URL needs "RTX 3080" vs "RTX_3080", the user won't know and likely won't care to know.
The argparse library would be a very good option to implement the command line use for the user.
Thoughts on the use of this feature @wandersonca@ChiffX ? I can start the work on this over the next few days.
The text was updated successfully, but these errors were encountered:
Yes, that would work. I've also seen people use docopt. You write out the help in a special way and the parser is generated. I don't have a lot of experience with either.
That or we continue using environment variables, it lends itself well to Docker. docker run -e component=3080 followed with a os.getenv("component").
Interesting, I haven't heard of docopt before but I do have experience with argparse. I am a fan of Docker so I would support a design that allows easy use of it.
I have also wanted to move the search addresses into some form of constants file, I like the look of that YAML file.
It seems that this functionality can be added with minimal changes. It would be a good addition if the user could add one or more command line arguments such as:
--component = 3080
or
--component = RTX3080
I'm not sure if the parts would need to be on an internal list to match syntax properly. If the URL needs "RTX 3080" vs "RTX_3080", the user won't know and likely won't care to know.
The argparse library would be a very good option to implement the command line use for the user.
Thoughts on the use of this feature @wandersonca @ChiffX ? I can start the work on this over the next few days.
The text was updated successfully, but these errors were encountered: