microsoft / microsoft/microsoft-performance-toolkit-sdk
Enable manual data extension registration.
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 239
- Forks
- 78
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 2
Description
Is your feature request an entirely new concept?
Not entirely a new concept. This currently happens automatically when modules are dropped in the plugin folder. This will enable an extension to be manually registered without being in a certain folder.
Is your feature request related to an existing component?
Yes? There are extension discovery/repository component.
Is your feature request related to a problem? Please describe.
Not a problem per se... it just allows developers to easily extend a data source plugin in an executable, for example.
Additional context
We'd have to consider how this works when plugin isolation is used.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the extension discovery/repository component and the existing plugin-folder registration flow. Trace how plugin isolation affects discovery, then clarify the registration API and its behavior for extensions hosted directly in an executable. Done means a data source extension can be registered manually without residing in the plugin folder, with isolation behavior defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100