Skip to content
This repository has been archived by the owner on Jun 25, 2020. It is now read-only.

Use System.Composition.Convention to simplify plugin development & maintainance #353

Open
biohazard999 opened this issue Sep 30, 2019 · 3 comments
Open

Use System.Composition.Convention to simplify plugin development & maintainance #353

biohazard999 opened this issue Sep 30, 2019 · 3 comments

Comments

@biohazard999
Copy link
Contributor

To support plugin developers and reduce maintainance use System.Composition.Convention for some parts of the application (where it makes sense)

  • custom commands
  • argument and command binding
  • the pubic plugin API

relates #347
@biohazard999 biohazard999 mentioned this issue Sep 30, 2019
Merged
17 tasks
@laedit laedit self-assigned this Sep 30, 2019
@laedit
Copy link
Member

laedit commented Sep 30, 2019 •
edited
Loading

Thanks, you are the best!
I will review it as soon as I can.
EDIT: sorry, I am very tired, I thought that it was already the PR.

@laedit laedit removed their assignment Sep 30, 2019
@biohazard999 biohazard999 mentioned this issue Oct 2, 2019
Closed
@laedit
Copy link
Member

laedit commented Oct 4, 2019

Just to define the perimeter more precisely, if possible I want to handle all exports through conventions, in order to really simplify all extensibility.

@biohazard999
Copy link
Contributor Author

We can for sure get rid of most Exports but we need at least a little bit of metadata and for Imports/OnSatisfyImports I'm not sure, at least interfaces or match the PropertyTypes. But that can be tricky I guess.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@biohazard999 @laedit