AzureStorageExplorer
AzureStorageExplorer copied to clipboard
Where is the source code?
Source code isn't open yet, I'm afraid. But we may plan to open it up in the future. We're only using GitHub for issue tracking for the time being.
Leaving issue open to gauge interest.
For people thumbs upping this issue, feel free to comment with why you're interested in seeing the source code (you want to contribute, you're interested in seeing the inner workings, you want to be able to fork it, etc.)!
Here's the reasons I'd like to see the code made available:
- Allows the community to review the code & dependencies
- Allows the community to make minor changes
- Allows the community to contribute features that aren't as high of a priority for the team
- Gives a good reference for doing auth with 2fa
- Gives a good reference for using the node storage sdk
I'd definitely look through the code, not sure what else I'd personally do with it right now though.
@xt0rted Thanks! Comments like these are highly appreciated and can help us prioritize open sourcing with enough interest!
I'm very interested in contributing. I've already fixed a couple of bugs in the Javascript so I can connect to my local Cosmos DB Emulator because I'm using a different port. I would like to be able to submit PRs to fix these bugs so I, and others that are experiencing the same problem, don't have to keep figuring out how to hack a fix for them with the next version.
To second what @xt0rted said above, open sourcing this code provides a great reference for using all the Azure SDKs that this tool uses (in which our company is quite interested). Also, it would be very nice if the community could contribute to the fixes that aren't a priority to the Azure Storage Explorer team but are definitely a priority to their own company.
Thanks for the tool! We're pretty much an Azure shop, so it's quite helpful to us. Keep up the good work.
It's a great tool and I was surprised from the beginning that it wasn't open source. I would like to see how the code is organized and how the SDKs are managed/used. Would be good to contribute directly to fixing bugs and adding features.
Hi @craxal, we are in the future of your 3-may-2018 comment! :D Are any update in the planes to open the source code?
best regards.
@manuelvalenzuela Thanks for your interest! Afraid I don't have any updates as of yet. But this is still on our radar.
Keep the comments coming! If our users keep asking for this, we can bump it up our priority list.
in storage explorer i see paging is implemented for azure table storage. i want to understand the code to see how the paging is implemented in the explorer, like wise many features are there in the explorer which developers want to implement in their projects. please make the code as open source, developers will have understand best practices and to be followed by seeing your code as reference for accessing the azure storage, this will help all the developers
@kkbandaru thanks for your interest. As Craig has mentioned above open source is on our long term plan. We haven't had the time to work on it yet.
Reopening. Not sure why this was closed, even though this is a long-term plan. We should close only when Storage Explorer has actually been open sourced.
Looking to be able to perform source mirroring and some update control for enterprise deployment
Really useful tool, would be very interested in looking through the source code.
I want to contribute translate to Japanese.
@tsubasaxZZZ Thanks for the offer. We are in the process of making the code base localizable. JPN will be one of the languages to be localized to. Stay tuned.
I would like to see this open sourced because I'd like to help contribute.
I've been working with Azure Storage Explorer since one of its earliest versions somewhere in 2015. I would like to see this open sourced because I would like to ...
- help contribute technically
- help contribute translate into Dutch
- see the inner workings of Azure Storage Explorer
Where is the open source version?
@alexgman As stated in the comments above, Storage Explorer source code is not yet open, but we have log-term plans for making it so.
Just want to chime in that I would appreciate open-sourcing the code as well. Right now, most people in our company cannot use the explorer since you need admin rights to install - and we can't do anything about it.
We haven't had the time to work on it yet.
Wouldn't open-sourcing this actually save you time? People waiting desperately for you to implement some function might just decide to implement it for you ;-)
here is a happy volunteer 🙋🏻♂️
@kasuteru FYI, #1108 is tracking the issue you mentioned.
@craxal thanks for the update on that issue, I knew about #1108 but forgot to follow it.
I would like to see this open sourced:
- I would definitely contribute by fixing bugs or implementing small features.
- I think it is useful to see master branch and what to expect in next releases.
- I found it very useful several times when I was able to go through Devs discussion on PRs. Makes thinks much more clearer and more easily understandable.
https://github.com/microsoft/AzureStorageExplorer/issues/626 The motivator for me to contribute to the source code.
I'd like the source code to be open due to issue #245 where-by the node module "request" does not support NTLM proxy authentication, so I may fork the code and replace "request" with a http library that is NTLM proxy aware.
The code currently is not in the state to be open sourced unfortunately.
@jusso-dev We actually have some plans in the works to get this fixed. The problem is more than just switching to an NTLM-aware networking library. We also have to make sure other libraries we use that make network calls will still work (for example, the Azure Storage client library). We asked them about this, and new versions allow us to effectively inject our own networking library into their pipeline.
One of the new features may be a page with properties where users can set the behavior of Storage Explorer. Now, I see the one where I can mark that I want to upload files always with overwrite option, but without to be prompted every time.