Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Recommended formatter, Prettier, indents block sequences #588

Open
siewers opened this issue Jun 20, 2024 · 0 comments
Open

Recommended formatter, Prettier, indents block sequences #588

siewers opened this issue Jun 20, 2024 · 0 comments
Labels
Area: VsCodeExtension question Further information is requested

Comments

@siewers
Copy link

siewers commented Jun 20, 2024

According to the documentation on Azure Pipeline formatting, block sequences should not be indented:

parameters:
- name: param1
  type: string
- name: param2
  type: string

However, using the Prettier formatter, the sequences are indented:

parameters:
  - name: param1
    type: string
  - name: param2
    type: string

The Prettier maintainer has a clear philosophy and will not make any exceptions (see related issue), which makes sense.

However, as the issue describes, we're stuck between using a formatter that works with the Azure Pipelines extension and none (the default behaves similarly and does the same indentation).
So, currently, it's impossible to use a formatter if we want to adhere to the standard described throughout the documentation.

As explained in this issue, the redhat.vscode-yaml formatter won't work if the file types are azure-pipelines as it only accepts yaml.

Do you know if there are any plans to use a different formatter, or what is your recommendation?

@DenisRumyantsev DenisRumyantsev added question Further information is requested and removed triage labels Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: VsCodeExtension question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants