dvc-back-end-wrappers is a central list of dispatching functions, but it is currently only partial.
What is the policy on what functions should be in that list? The list is used in dvc-register-dvc to automatically generate wrapper functions that set dvc-temp-current-active-dvc and then call the function in the list. The point of these automatically generated wrappers is to make it easy to call dvc dispatching functions while specifying a particular back-end, for the case where a user has a workspace that is maintained in two (or more) back-ends. Thus it would seem reasonable that _all_ dispatching functions that are interactive should be in dvc-back-end-wrappers. Is that the intent? This could prove troublesome; dvc-back-end-wrappers has the argument list as well as the name, so any change to the actual function's argument list must also be made in dvc-back-end-wrappers. It would be nice to be able to check or enforce that automatically, but I suspect that's not possible. We should at least put a comment at each function definition that says "also update dvc-back-end-wrappers". -- -- Stephe _______________________________________________ Dvc-dev mailing list [email protected] https://mail.gna.org/listinfo/dvc-dev
