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 want to simplify the user experience, so that when type a command like "Minnesota-immunization-data-pipeline query" they should be prompted for the information that is missing. There are especially 3 types of prompts. There are text input prompts, there are file/folder input path prompts, and there are password prompts.
AC
all arguments beyond the top level ("extract" "load" "transform") should be able to be prompted for.
prompting should never be required, important for the case where you are using the script from a non-interactive environment
unit tests should cover this behavior. You can just mock the argparse library the test this.
integration tests are reasonable here too, but I'm not sure that they are necessary. Maybe one that just checks if the user can use prompting at all
The text was updated successfully, but these errors were encountered:
I want to simplify the user experience, so that when type a command like "Minnesota-immunization-data-pipeline query" they should be prompted for the information that is missing. There are especially 3 types of prompts. There are text input prompts, there are file/folder input path prompts, and there are password prompts.
AC
The text was updated successfully, but these errors were encountered: