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

Failure to parse .editorconfig file #3955

Closed
1 task done
s3igo opened this issue Sep 17, 2024 · 1 comment
Closed
1 task done

Failure to parse .editorconfig file #3955

s3igo opened this issue Sep 17, 2024 · 1 comment

Comments

@s3igo
Copy link

s3igo commented Sep 17, 2024

Environment information

CLI:
  Version:                      1.9.1
  Color support:                true

Platform:
  CPU Architecture:             aarch64
  OS:                           macos

Environment:
  BIOME_LOG_PATH:               unset
  BIOME_LOG_PREFIX_NAME:        unset
  BIOME_CONFIG_PATH:            unset
  NO_COLOR:                     unset
  TERM:                         "wezterm"
  JS_RUNTIME_VERSION:           "v20.17.0"
  JS_RUNTIME_NAME:              "node"
  NODE_PACKAGE_MANAGER:         "bun/1.1.27"

Biome Configuration:
  Status:                       Loaded successfully
  Formatter disabled:           false
  Linter disabled:              false
  Organize imports disabled:    false
  VCS disabled:                 true

Workspace:
  Open Documents:               0

What happened?

Editorconfig support generates the following error if the .editorconfig file contains a section with * in it.

biome.json

{
    "formatter": {
        "useEditorconfig": true
    }
}

.editorconfig

root = true

[*.md]
max_line_length = off
trim_trailing_whitespace = false

Output of $ bunx @biomejs/biome check.

configuration ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ✖ Failed to parse the .editorconfig file.

    Caused by:
      Custom("invalid digit found in string")

Expected result

It should not throw an error.

Code of Conduct

  • I agree to follow Biome's Code of Conduct
@ematipico
Copy link
Member

Duplicate of #3904

@ematipico ematipico marked this as a duplicate of #3904 Sep 17, 2024
@ematipico ematipico closed this as not planned Won't fix, can't repro, duplicate, stale Sep 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants