microsoft / microsoft/AzureStorageExplorer
Storage Explorer Extensibility Preview
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 452
- Forks
- 92
- Avg merge
- 15h 20m
- Merged PRs (30d)
- 3
Description
Hello everyone! We're looking for developers who would be interested in creating Storage Explorer extensions.
We want to preview the writing of Storage Explorer extensions to those who are interested. For this preview, you would be able to create extensions that build on top of existing Storage Explorer features and experiences. For example, adding an action to the context menu of the blob explorer. Clicking the action would trigger your extension and allow you to run your code against your data in Azure Storage.
If you are interested in being a part of this preview, please take this survey: https://aka.ms/storageexplorer/extensibilityprivatepreviewsurvey
FAQ:
What languages are extensions written in?
Extensions are primarily written using JavaScript and HTML.
Do I need to know how to code to participate in the preview?
Yes. We are looking for those with existing coding experience.
Do I need to have an existing idea for an extension?
Yes. We will not be providing ideas for you.
What types of extensions are you looking for?
We're looking for extensions that build on top of existing Storage Explorer features and experiences. For example:
- Adding actions to the blob explorer context menu
- Adding actions to the blob container context menu
- Doing something after an upload/download finishes
Contributor guide
No contributing guide indexed for this repository
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
This issue is a recruitment notice for a Storage Explorer extensibility preview, not a defined code task. Start with the linked survey and the stated examples, such as blob explorer context-menu actions or upload/download callbacks; there is no named file, test, or completion criterion in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html, javascript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100