Skip to content

✨ Extension Store #183

Open
Open

Description

@jasonplatts

Overview

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)

Tasks

  • Determine storage requirements
  • Design extension store UI (✨ Extension Navigator #355)
  • Build extension submission process
  • Build library, using information in submitted extension manifest files.

Concept

01-macOS-code-edit-extensions-installed

02-macOS-code-edit-extensions-explore

I'd imagine when one is clicked a tab in the main content area opens up to show more details.

Activity

  1. nanashili commented on Mar 22, 2022

    @nanashili
    Contributor

    Do we need a backend for this if so i know someone who might help with this

  2. austincondiff commented on Mar 22, 2022

    @austincondiff
    Collaborator

    We are definitely not going to call it a "Marketplace". That is Microsoft lingo 😁

  3. jasonplatts commented on Mar 22, 2022

    @jasonplatts
    CollaboratorAuthor

    We are definitely not going to call it a "Marketplace". That is Microsoft lingo 😁

    haha! I couldn't remember what you called it. We should definitely update it.

  4. austincondiff commented on Mar 22, 2022

    @austincondiff
    Collaborator

    @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?

  5. jasonplatts commented on Mar 22, 2022

    @jasonplatts
    CollaboratorAuthor

    @austincondiff, would you be able to post the screens you showed me?

  6. nanashili commented on Mar 22, 2022

    @nanashili
    Contributor

    @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

  7. added
    extensionsIssues related to the extension architecture in CodeEdit
    on Mar 22, 2022
  8. changed the title [-]Add Extension Marketplace[/-] [+][FEAT] Add Extension Marketplace[/+] on Mar 22, 2022
  9. austincondiff commented on Mar 22, 2022

    @austincondiff
    Collaborator

    @austincondiff, would you be able to post the screens you showed me?

    Posted to the issue description

  10. austincondiff commented on Mar 22, 2022

    @austincondiff
    Collaborator

    @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!

  11. nanashili commented on Mar 22, 2022

    @nanashili
    Contributor

    @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

  12. jasonplatts commented on Mar 22, 2022

    @jasonplatts
    CollaboratorAuthor

    "Extension Library" anyone? (similar to App library)

    I like it. Simple and clear.

  13. jasonplatts commented on Mar 22, 2022

    @jasonplatts
    CollaboratorAuthor

    @austincondiff, would you be able to post the screens you showed me?

    Posted to the issue description

    Thanks!

  14. 17 remaining items

  15. austincondiff commented on Apr 28, 2022

    @austincondiff
    Collaborator

    @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…

    1. It follows Apple’s naming conventions (I.e. “App Store”, “App Library”)
    2. 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.

  16. jasonplatts commented on Apr 28, 2022

    @jasonplatts
    CollaboratorAuthor

    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.

  17. prashantvc commented on Apr 29, 2022

    @prashantvc
    Contributor

    @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.

  18. jasonplatts commented on May 2, 2022

    @jasonplatts
    CollaboratorAuthor

    Sounds great @prashantvc! Thank you!

  19. deleted a comment from stale on Jul 2, 2022
  20. removed
    wontfixThis will not be worked on
    on Jul 2, 2022
  21. cavnit commented on Jan 7, 2024

    @cavnit

    @austincondiff happy to throw my hat in the ring for the store backend in swift :) (Vapor)

  22. austincondiff commented on Jan 7, 2024

    @austincondiff
    Collaborator

    @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.

  23. matthijseikelenboom commented on Jan 7, 2024

    @matthijseikelenboom
    Contributor

    @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.

  24. austincondiff commented on Jan 7, 2024

    @austincondiff
    Collaborator

    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!

  25. prashantvc commented on Jan 8, 2024

    @prashantvc
    Contributor

    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

  26. cavnit commented on Jan 8, 2024

    @cavnit

    Sorry for the slow response, I will put something together over the next couple of days

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    UIThis is UI relatedclarification neededFurther information is requestedenhancementNew feature or requestextensionsIssues related to the extension architecture in CodeEdit

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions