You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A lot of editors these days, such as VSCode, have built-in behaviour to convert tab presses into whitespace.
While just about every language allows whitespaces for indentation, not every allows tabs - the notable one being YAML.
Users of today's code editor in Octopus can't rely on pressing tab to indent their YAML code as it will not conform to the YAML syntax standard. Instead they have to either rely on other tools to convert those tabs to whitespaces (which detracts from the usefulness of having a code editor in Octopus), or they have to indent using the spacebar which is more tedious.
The code editor in Octopus should bind tab key presses to equivalent whitespace spacing instead. This will bring the experience of the code editor more in line with other popular editors.
The text was updated successfully, but these errors were encountered:
kevjt
added
the
kind/enhancement
This issue represents an enhancement we are committed to adding to Octopus as some time
label
May 7, 2024
A lot of editors these days, such as VSCode, have built-in behaviour to convert tab presses into whitespace.
While just about every language allows whitespaces for indentation, not every allows tabs - the notable one being YAML.
Users of today's code editor in Octopus can't rely on pressing tab to indent their YAML code as it will not conform to the YAML syntax standard. Instead they have to either rely on other tools to convert those tabs to whitespaces (which detracts from the usefulness of having a code editor in Octopus), or they have to indent using the spacebar which is more tedious.
The code editor in Octopus should bind tab key presses to equivalent whitespace spacing instead. This will bring the experience of the code editor more in line with other popular editors.
The text was updated successfully, but these errors were encountered: