Currently whitespace characters are not shown in polacode.
This would be very useful for screenshots of themes and linters.

Is it possible to enable rendering of those in the screenshots?

• I have searched through existing issues
• I have read through docs
• I have read FAQ

Info

• Platform: Linux
• Vetur version: 0.0.61
• VS Code version:

As soon as VScode was updated to 1.31.0, it appears that this prettier extensions conflicts with the the built-in organize imports setting, when organize imports on save is enabled.

prettier: "prettier": "^1.16.4", (was initially on 1.13.7, tried to update)
vscode: Version 1.31.0 (1.31.0)
extension: 1.8.0

I first opened a ticket with vscode core, but was referred to the extension a

The doc says it is installed by default with a supported workload, but on my install this wasn't true. After looking for the options a while, I realized it wasn't installed and had to manually install the component via the installer. The docs should have some instructions in case other folks are in this predicament.

Document Details

⚠ *Do not edit this section. It is required for docs.m

Is your feature request related to a problem? Please describe.
Current vscode built in debugger accepts a launch.json file in the workspace where additional arguments can be added.

Describe the solution you'd like
I'd like similar functionality, or a pointer to how to do it (looked through documentation - didn't see anything).

Also useful would be the ability to request args if non

Setting peacock.color or peacock.remoteColor in the user settings.json can be done manually. If set, peacock will use that color as the default color to colorize VS Code.

This should be documented in the readme, along with considerations.

Considerations:

• this can only be set or unset manually.
• this will make every vs code instance that doesnt have a color in their workspace use t

Example:

/** @var string $str */
 $str = 1;

At the end of this snippet $str is inferred as string. It'd be really useful if violations to user specified types were highlighted.

A while ago I setup and studied this extension source code.
Today downloaded the source code again but I was unable to recall how to setup and start debugging it. I couldn't even remember where I read how to do it. It would be nice to have more extensive startup guide for new developers.

Describe the bug
I think that title is clear enough. While you are creating pages, parts are not filled with the ApplicationArea property, and the subpages are not shown. I think this should be solved in order to avoid errors.

Versions:

• AL Language: 3.0.145991