kiliantyler / kubernetes-yaml-formatter-x Goto Github PK

It is currently a bit scattered and probably doesn't need to be as complex as it needs to be

It would also be nice to have each step as its own action instead of one giant file (if possible)

Tests should be run in the actions workflow

(blocked by #25 )

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• fix(deps): update @types/node ( 20.12.7 → 20.12.12 )
• fix(deps): update @vscode/test-electron ( 2.3.9 → 2.3.10 )
• fix(deps): update glob ( 10.3.12 → 10.3.16 )
• feat(deps): update @types/vscode ( 1.88.0 → 1.89.0 )
• feat(deps): update typescript-eslint monorepo ( 7.6.0 → 7.10.0 ) (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• feat(deps)!: Update eslint ( 8.57.0 → 9.3.0 )
• feat(github-release)!: Update pre-commit hook pre-commit/mirrors-eslint ( v8.56.0 → v9.3.0 )
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

When tagged for a version automation should not just upload the vsix package to the extension markerplace but also into this repo with a release created for the packages.

This just keeps in line with open software allowing users to download extensions from the git repo without relying on the marketplace

It would be nice for Renovate to automatically PR a new yamlfmt release.

It currently only lives in the action file when it downloads the repo, there might be a way to have renovate detect this file but it needs to be investigated how to do do.

Currently testing doesn't work, it should

Upstream yamlfmt has an option for -global_conf which will pull all settings from a globally defined config file.
It would be nice if this option existed in the extension

https://github.com/google/yamlfmt/blob/v0.11.0/docs/command-usage.md#operation-flags

Get some generalized updates into the packages to start modernizing this

Extension 'kiliantyler.kubernetes-yaml-formatter-x' uses a document selector without scheme. Learn more about this: https://go.microsoft.com/fwlink/?linkid=872305

Get precommit running in the repo

Instead of creating and reading from a config file in the extension, use an existing .yamlfmt (or yamlfmt.yaml or yamlfmt.yml) file from within the project

This would also require a setting to allow this to override editor settings, for example:

• yamlfmt.yaml exists in folder
• Options in yamlfmt.yaml do not match options set in extension settings
• Extension has an override setting that allows the in-code yamlfmt.yaml to be used

Optionally this could be disabled to force formatting the way the extension is configured.

With no yamlfmt.yaml config file present, extension settings would be used (or global settings, see: #23 )

Presidence (Highest wins):

• .yamlfmt (in folder)
• yamlfmt.yaml (in folder)
• yamlfmt.yml (in folder)
• Global settings (if enabled)
• Extension settings