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
Currently GitRepository uses MepoState to get the full local path of the fixture, in order to construct the full local path of a sub-component, which are specified in the registry in relative form. Maybe there is a better way to get the full local path of the fixture that doesn't require dependence on MepoState.
One consequence of git.py's dependence on MepoState is that we need two separate copies of get_current_remote_url - one in git.py and the other in component.py, to avoid circular dependency. Once #312 is implemented, the need for get_current_remote_url goes away, but it will still be good to find a way to remove this dependence.
The text was updated successfully, but these errors were encountered:
Currently
GitRepository
usesMepoState
to get the full local path of the fixture, in order to construct the full local path of a sub-component, which are specified in the registry in relative form. Maybe there is a better way to get the full local path of the fixture that doesn't require dependence onMepoState
.One consequence of
git.py
's dependence onMepoState
is that we need two separate copies ofget_current_remote_url
- one ingit.py
and the other incomponent.py
, to avoid circular dependency. Once #312 is implemented, the need forget_current_remote_url
goes away, but it will still be good to find a way to remove this dependence.The text was updated successfully, but these errors were encountered: