Skip to content

Custom Indentation #289

Open
Open
@TGekko

Description

I made a feature request/suggestion regarding the Edge DevTools extension for VSCode on the extension's GitHub page. I was told that it would be best to make the same suggestion here, and I was given this link. The change would need to be made to the DevTools themselves.

To summarize the suggestion: I believe it would be useful to have the ability to customize the console's custom indentation minutely, allowing for a custom number of spaces (zero or more). I prefer one space. Microsoft Edge DevTools only allows for 2, 4, or 8 spaces or a Tab character, and I have always found that using only one space saves both space and time -- especially with code as temporary as that which is written in the console. I have quoted the original suggestion below and thank you for your consideration:

Is your feature request related to a problem? Please describe.
I would like to request the possibility to customize the "Default indentation" of the DevTools console minutely (1 or more spaces or a tab character).
I prefer single space indentation and that isn't possible in the DevTools console in Microsoft Edge or in the vscode extension.

Describe the solution you'd like:
Synchronize the console's indentation settings with the user's vscode indentation settings, or add settings similar to vscode's indentation settings to the DevTools extension.

Describe alternatives you've considered:
I considered using the DevTools console window in Microsoft Edge, but its indentation settings are limited to "2 spaces", "4 spaces", "8 spaces" or "Tab character" and doesn't have an additional setting for rendering the tab character with a custom width.
If the Microsoft Edge DevTools had "1 space" as an option, that would fix the problem too.

Additional context:
It might be useful to note that the settings found in Microsoft Edge do not seem readily available in the vscode extension, -- I couldn't find them, -- and enabling "sync settings" didn't seem to affect the console either. Adding access to these DevTools settings wouldn't solve the issue, but it seemed noteworthy.

AB#55004586

Metadata

Assignees

No one assigned

    Labels

    featureNew feature or requesttrackedThis issue is now tracked on our internal backlog

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions