Skip to content

Conversation

@martijn00
Copy link
Contributor

@ebozduman
Copy link
Collaborator

@martijn00 ,

Will do the review in during CA work hours...

Copy link
Collaborator

@ebozduman ebozduman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@martijn00

Could you add some explanation/information about this PR, like what inheritance issue is fixed by this PR and why service collection is added, what is it going to help/solve etc, briefly in just one or two sentences?

@martijn00
Copy link
Contributor Author

The IMinioClient interface didn't inherit the 2 other interfaces, but the implementation did implement them. For that reason the methods in the interface were also duplicated. I've removed that.

I'm now working towards a more interface based implementation of minio so that it the standard DI container of .net can use it.

This is a first step towards an easier way to implement Minio. You can call AddMinio in your normal api build and resolve IMinioClient or IMinioClientFactory through DI or the service locator after that

Copy link
Collaborator

@ebozduman ebozduman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants