| Thanks for the response, Mark. Yes, the UI you describe does sound like quite a lot of work. I'd be happy with a simpler alternative, e.g. where the user can enter the module path themselves in a text box and there was a warning or error reported when the build ran if that module path was not present. I feel this would be fairly easy to implement and would certainly handle my use-case. I consider sparse checkout a disk space optimisation, so the consequences of incorrect configuration are less severe than other submodule parameters. What do you think about this option? |
