You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The extension store should allow users to browse and install extensions submitted by other developers. They should be categorized using the information provided in each extensions manifest.json (See #174)
@nanashili I'd imagine so. We need to choose the right technologies to use for our backend. We will have our own website for downloads help and documentation so maybe Node.js?
@nanashili I'd imagine so. We need to choose the right technologies to use for our backend. We will have our own website for downloads help and documentation so maybe Node.js?
I can put you in contact with someone that builds in back-end
@nanashili I'd imagine so. We need to choose the right technologies to use for our backend. We will have our own website for downloads help and documentation so maybe Node.js?
I can put you in contact with someone that builds in back-end
@nanashili I'd imagine so. We need to choose the right technologies to use for our backend. We will have our own website for downloads help and documentation so maybe Node.js?
I can put you in contact with someone that builds in back-end
Bring him on the project!
What about .net as the back-end it has way better performance when it comes to scaling
My thought in using the term “store” for the repository of extensions and “library” for the users installed extensions is…
It follows Apple’s naming conventions (I.e. “App Store”, “App Library”)
It doesn’t necessarily denote the exchange of funds quite the same way the term “marketplace” does (I could be wrong here though). In my line of thought, “store” can mean a store of value, a store of code, a store of functionality etc. When I look up store I see synonyms like, supply, reserve, cache, warehouse, storehouse, shed etc.
We certainly however wouldn’t mind hearing any expertise you have on the subject here or help on our backend when it comes down to it. We’d need to discuss architecture first though and I’d invite you to create an issue for the Extension Store Backend Architecture to get the conversation going.
@jasonplatts VS Code team is going to host Extension Authors meet soon. I will drop the details in here once available, you can join in ask questions. The team is extremely open, you can ask questions related to APIs and architecture.
@cavnit thay would be great! Feel free to put together a POC. Let us know if you need anything along the way. If you would like help or feedback, feel free to collaborate with other contributors and maintainers on our Discord.
@cavnit We don't have any requirements regarding this at this moment. Without the requirements it will be difficult to build without wasting time and build things that we maybe don't even want. There are some things described here, but due to the fact that this has been put on the back burner, I don't know how relevant these are at the moment.
Perhaps we can discuss these during our next meeting on our Discord.
We still welcome the help though. Your thoughts and ideas on how we could do this would be appreciated. Community by-in would be great so it might be a good idea to have a discussion in our extension channel in discord to exchange ideas and solidify requirements. We can discuss it in next weeks meet up but we don’t necessarily need to wait for it. I’d love to get the ball rolling!
I built a private extension repo for VS Code here https://github.com/prashantvc/extensions
We can extend on this, right now it is elementary. I can help you draft a initial requirements for the extension repo
Activity
nanashili commentedon Mar 22, 2022
Do we need a backend for this if so i know someone who might help with this
austincondiff commentedon Mar 22, 2022
We are definitely not going to call it a "Marketplace". That is Microsoft lingo 😁
jasonplatts commentedon Mar 22, 2022
haha! I couldn't remember what you called it. We should definitely update it.
austincondiff commentedon Mar 22, 2022
@nanashili I'd imagine so. We need to choose the right technologies to use for our backend. We will have our own website for downloads help and documentation so maybe Node.js?
jasonplatts commentedon Mar 22, 2022
@austincondiff, would you be able to post the screens you showed me?
nanashili commentedon Mar 22, 2022
I can put you in contact with someone that builds in back-end
[-]Add Extension Marketplace[/-][+][FEAT] Add Extension Marketplace[/+]austincondiff commentedon Mar 22, 2022
Posted to the issue description
austincondiff commentedon Mar 22, 2022
Bring him on the project!
nanashili commentedon Mar 22, 2022
What about .net as the back-end it has way better performance when it comes to scaling
jasonplatts commentedon Mar 22, 2022
I like it. Simple and clear.
jasonplatts commentedon Mar 22, 2022
Thanks!
17 remaining items
austincondiff commentedon Apr 28, 2022
@prashantvc First of all, welcome to CodeEdit!
My thought in using the term “store” for the repository of extensions and “library” for the users installed extensions is…
We certainly however wouldn’t mind hearing any expertise you have on the subject here or help on our backend when it comes down to it. We’d need to discuss architecture first though and I’d invite you to create an issue for the Extension Store Backend Architecture to get the conversation going.
jasonplatts commentedon Apr 28, 2022
Thanks @prashantvc for the suggestion and offering to help with building the backend! We very much appreciate it.
We would also love to hear any feedback and/or insight you or your team can provide on the extension architecture or CodeEdit in general.
prashantvc commentedon Apr 29, 2022
@jasonplatts VS Code team is going to host Extension Authors meet soon. I will drop the details in here once available, you can join in ask questions. The team is extremely open, you can ask questions related to APIs and architecture.
jasonplatts commentedon May 2, 2022
Sounds great @prashantvc! Thank you!
cavnit commentedon Jan 7, 2024
@austincondiff happy to throw my hat in the ring for the store backend in swift :) (Vapor)
austincondiff commentedon Jan 7, 2024
@cavnit thay would be great! Feel free to put together a POC. Let us know if you need anything along the way. If you would like help or feedback, feel free to collaborate with other contributors and maintainers on our Discord.
matthijseikelenboom commentedon Jan 7, 2024
@cavnit We don't have any requirements regarding this at this moment. Without the requirements it will be difficult to build without wasting time and build things that we maybe don't even want. There are some things described here, but due to the fact that this has been put on the back burner, I don't know how relevant these are at the moment.
Perhaps we can discuss these during our next meeting on our Discord.
austincondiff commentedon Jan 7, 2024
We still welcome the help though. Your thoughts and ideas on how we could do this would be appreciated. Community by-in would be great so it might be a good idea to have a discussion in our extension channel in discord to exchange ideas and solidify requirements. We can discuss it in next weeks meet up but we don’t necessarily need to wait for it. I’d love to get the ball rolling!
prashantvc commentedon Jan 8, 2024
I built a private extension repo for VS Code here https://github.com/prashantvc/extensions
We can extend on this, right now it is elementary. I can help you draft a initial requirements for the extension repo
cavnit commentedon Jan 8, 2024
Sorry for the slow response, I will put something together over the next couple of days