Git Product home page Git Product logo

Comments (5)

raycastbot avatar raycastbot commented on July 27, 2024

Thank you for opening this issue!

🔔 @thomaspaulmann @iainsimmons @macbookandrew @cy-98 @immint023 @pernielsentikaer @vimtor @tonka3000 @aka-rabbi-inv @oilbeater @QIanGua @hakob8956 @erics118 you might want to have a look.

💡 Author and Contributors commands

The author and contributors of thomas/visual-studio-code can trigger bot actions by commenting:

  • @raycastbot close this issue Closes the issue.
  • @raycastbot rename this issue to "Awesome new title" Renames the issue.
  • @raycastbot reopen this issue Reopen the issue.

from extensions.

erics118 avatar erics118 commented on July 27, 2024

To debug, could I get a bit more information?

  • Do you use VSCode, or some similar variant, eg Cursor, VSCodium?
  • It could be that one of the extensions has a broken manifest. Could you provide a list of all your installed extensions? You can do this with:
code --list-extensions
  • Do you have any extensions installed via a different means than the VSCode extension marketplace?

from extensions.

tonka3000 avatar tonka3000 commented on July 27, 2024

@erics118

There is a high chance that @ashchen738 has a local installed extension which does not contain a metadata field (this get injected from the "install via store") and therefore there is no publisherId.

The fix should be straight forward. Make metadata optional (e.metadata?.publisherId instead of e.metadata.publisherId) here and here.
Also mark metadata as nullable as well as here and here.

It seems that I forget that only store based extension have these fields when I impl. that feature.

from extensions.

ashchen738 avatar ashchen738 commented on July 27, 2024

@erics118

There is a high chance that @ashchen738 has a local installed extension which does not contain a metadata field (this get injected from the "install via store") and therefore there is no publisherId.

The fix should be straight forward. Make metadata optional (e.metadata?.publisherId instead of e.metadata.publisherId) here and here. Also mark metadata as nullable as well as here and here.

It seems that I forget that only store based extension have these fields when I impl. that feature.

I think this sounds about right. I do have a locally installed extension.

from extensions.

tonka3000 avatar tonka3000 commented on July 27, 2024

@ashchen738 I made a fix for the issue (#9888). Maybe you can check if it fix your issue.

from extensions.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.