Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split VCS Provider into several smaller provider interfaces #629

Open
AdmiringWorm opened this issue Oct 17, 2024 · 0 comments · May be fixed by #631
Open

Split VCS Provider into several smaller provider interfaces #629

AdmiringWorm opened this issue Oct 17, 2024 · 0 comments · May be fixed by #631
Assignees
Labels
Milestone

Comments

@AdmiringWorm
Copy link
Member

Detailed Description

Currently we are using a single monolithic interface that all supported providers need to support, we should split out this interface into smaller more related interfaces that can be used to implement specific sections of a provider when needed.

Context

To be able to only support certain aspects of a provider, without having to reimplement the entire VCS provider interface.

Possible Implementation

N/A

Your Environment

  • Version Used: 0.18.0
  • Edition Used (.NET Core, .NET Framework): .NET Core
  • Operating System and version (Windows 10, Ubuntu 18.04): Windows
@AdmiringWorm AdmiringWorm added this to the Future milestone Oct 17, 2024
@AdmiringWorm AdmiringWorm self-assigned this Oct 17, 2024
@AdmiringWorm AdmiringWorm linked a pull request Oct 17, 2024 that will close this issue
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant