READ FIRST: Welcome to Visual Studio Code's Extension Community

[digitarald]

Community discussions is the place to discuss VS Code's extension platform, ask questions, help other members of the community, and get answers.

‼️ Discussions focus only on extension development to learn, experiment, and grow sustainably.

🙌 Ready to ask extension development questions? Start here!

Other places to participate with VS Code:

• 🔎 "Help: Report Issue" is VS Code's built-in command to 🐛 report bugs, 🐌 performance issues, and 💡 feature requests.
• 🏠 VS Code repo for triaging issues and upvoting feature requests, and contributing.
• 📚 StackOverflow for general VS Code questions.
• 💬 Extension Dev Slack for chatting with other extension authors.
• 🩻 Extension API Documentation and code samples for learning and contributing documentation improvements.

We need your participation

… to create a welcoming and inspiring community. Microsoft's Open Source Code of Conduct applies here, in short please be kind and remember that there are real people on the other side of the keyboard.

Also:

• As we begin to build this community, we ask that you limit conversations to the categories available (more categories will be released as the community grows!)

• Before opening a new discussion, please search existing posts to see if the topic thread already exists.

• Please do not use this as a place to @ your favorite VS Code contributor to get an extra bump on a feature request. Spoiler: it won't work.

FAQ

How can I help?
Answer questions with empathy and kindness. Keep the community welcoming by giving contructive feedback and reporting unacceptable behavior. Reach out if you like to help with moderation.

Why are there just categories for extension development?
We want to start small, and the extension author community is just the right size. Meanwhile StackOverflow continues to serve most other questions.

When will more categories be added?
As we learn what works well, tweak our moderation process, and see the community grow before expanding topics. If we see moderation becoming a burden on the team we will also consider take action.

[PEZ]

Such a wonderful initiative. Thanks for starting this forum!

[infinitepower18]

Is there any reason why it's on a separate repo rather than having the discussions on the main vscode repo?

[digitarald]

Mostly that we want to avoid mixing it up with the existing issue triage process (for now) and are considering adding more categories for topics that have their own repos, like remote, python, etc.

[gjsjohnmurray]

Happy discussing! :)

@digitarald please add a link to https://github.com/microsoft/vscode-discussions/discussions at the end of that line. Then when I point people at #5 from elsewhere (e.g. an issue in microsoft/vscode) they can more easily get started with "happy discussing!".

[water-bai]

• VS Code Version: 1.72.2
• OS Version: macOS 12.1 Monterey(13-inch, M1, 2020)

demo

demo-for-issue

my problem

it work normal when i am debugging.but when i publish, install and use command "issueDemo.showLint". it toast an error, like follow image

it work normal when i am debugging. eg:

[digitarald]

@baikaishui01 could you please file an issue for VS Code: https://github.com/microsoft/vscode/issues

[water-bai]

ok, thanks. This is very urgent for me. I hope you can reply as soon as possible. This is my issue: microsoft/vscode#165028

[ttax00]

middleware provideDocumentSymbols doesn't display children symbols
Concerning piece of code. https://code.visualstudio.com/api/language-extensions/embedded-languages
Calling the command on .html virtual document.

async provideDocumentSymbols(document, token, next) {
let result: undefined | DocumentSymbol[] = undefined;

result = await commands.executeCommand<DocumentSymbol[]>(
'vscode.executeDocumentSymbolProvider',
vdocUri(document),
);

return result;
}

this returns an array of DocumentSymbol[] which has children: DocumentSymbol[] properties. But vscode only display the top level symbols instead of everything. See screenshots here: ttax00/code-yew-server#2

Edit: A quick fix right now is to manually unpack the childrens into a flat DocumentSymbol array. Also, on startup, vscode.executeDocumentSymbolProvider would return undefined. And requires a few calls before the correct parse would be returned.

[gjsjohnmurray]

@TechTheAwesome I recommend starting a new discussion thread rather than commenting on the "Welcome" thread.

[ttax00]

I was linked to here when trying to make an issue on vscode 😅 I'm not too familiar with the project layout, so you meant moving the issue here? https://github.com/microsoft/vscode-discussions/discussions

[gjsjohnmurray]

Correct. There's a link from this thread which is intended to take you there:

[ttax00]

Thank you so much!

[sanjay51]

Hi - is there a way to disable vscode theming for webviews?
Details: https://stackoverflow.com/questions/74357614/vscode-webview-remove-default-styles

Thanks.

[gjsjohnmurray]

Please open a fresh discussion thread rather than branching from this Welcome thread. See above if you aren't clear how to do that.

[ruiminwang]

Is there any SDK/API to pop up the changelog once our extension is updated in customer's VS Code?

[r3m0t]

It is against the UX guidelines, but you can store your version number in ExtensionContext.globalState and check if it's gone out of sync with your ExtensionContext.extension.packageJSON.version. Or it's better to use a version number in your source code that you only increment when there is a significant changelog entry

[r3m0t]

Oh, I might be misremembering - here's the guidelines https://code.visualstudio.com/api/ux-guidelines/notifications

[aayush420]

Is there a way to get the CommentThread given the range and the document? It would be useful to add comments programmatically, rather than using the UI element on the line number column.

[gjsjohnmurray]

Is there a way to get the CommentThread given the range and the document? It would be useful to add comments programmatically, rather than using the UI element on the line number column.

@aayush420 please start a new discussion instead of adding your comment to this "Welcome" discussion.

[aayush420]

#336

[abhikp98]

I was using vs code to run Python codes. So I used a simple function to do some operations which have one argument. But inside function the argument's features are not getting listed or suggesting...
Installed extensions are
Python
Pylance
Autopep8
PyLint

[gjsjohnmurray]

@abhikp98 based on the information at the start of this thread, please seek assistance with your issue elsewhere. In your case the Pylance extension support channel might be a good place to begin.

[abhikp98]

I have already added Pylance.
For example:
def test(value):
value. # Here after putting dot, the features of string should come right? capitalise, count...

data = 'github'
test(data)

[gjsjohnmurray]

As you are not developing an extension for VS Code this is not the correct place for your help request. Please see above.

[Priyanshukeshri]

[gjsjohnmurray]

@Priyanshukeshri I recommend starting a new discussion thread rather than subverting the "Welcome" thread.

[plrubbo]

Hello, anyway could help me setting up an expo in Visual Studio Code?

[CuriousDev289]

@digitarald - How can I get the line number when hover on variable while using Vs code debugger extension for external debugging?

I am developing a custom debugger extension , when I started working on on-hover variable while debugging any program, I found that, there is no option to get line number to get the context along with value of the particular variable.

[xaxazak]

When will more categories be added? As we learn what works well, tweak our moderation process, and see the community grow before expanding topics. If we see moderation becoming a burden on the team we will also consider take action.

Have you had enough time to learn what works well?
Will you consider adding more forums now, such as:

• vscode development (not extensions).
• vscode help (perhaps separate categories for "getting started+installation", "general usage").
• general (community, metadiscussion, software suggestions, etc).

[digitarald]

It's a lot to manage and we are a small team. We still need to see how well this community supports itself and helps each other.

[TPJelf]

Extension Dev slack link is dead.

[digitarald]

Fixed, should work again

[gjsjohnmurray]

@digitarald I'd like to suggest some edits to this issue which may help reduce the number of threads which get started here that are not related to extension development.

1. I propose changing the title of this thread to "README FIRST before posting here". It's good that it is pinned, but I suspect some people aren't motivated to read something titled "Welcome to Visual Studio Code's Community Discussions".

2. Rephrase and restructure the first part of the post. My suggestion is:

This is a place to discuss VS Code's extension platform, ask questions about extension development, help other extension developers, and get answers.

We are initially scoping discussions to** just extension development** to learn, experiment, and grow sustainably.

Other places to participate with VS Code:

... (as before)

🙌 Ready to ask extension development questions? Start here!

We need your participation
... (as before)

3. Lock this thread (assuming GitHub Discussions supports locking).

[digitarald]

Done, great ideas – lets hope more people read the right parts. Thanks for helping to manage and grow this community!