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

🐛 biome won't respect config when executed from a parent directory #4246

Closed
1 task done
jaysonsantos opened this issue Oct 10, 2024 · 1 comment
Closed
1 task done
Labels
S-Needs triage Status: this issue needs to be triaged

Comments

@jaysonsantos
Copy link

Environment information

CLI:
  Version:                      1.9.2
  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:                         "alacritty"
  JS_RUNTIME_VERSION:           unset
  JS_RUNTIME_NAME:              unset
  NODE_PACKAGE_MANAGER:         unset

Biome Configuration:
  Status:                       unset

Workspace:
  Open Documents:               0

What happened?

create the following structure
project/sub/{biome.jsonc,my-file.js}
then from project run biome check sub

Expected result

In my view, it should respect that project/sub has a config and load it, instead of ignoring.
This is happens on a monorepo (without the extends usage) and commonly breaks formatting when running with pre-commit, which runs from the repository's root

Code of Conduct

  • I agree to follow Biome's Code of Conduct
@jaysonsantos jaysonsantos added the S-Needs triage Status: this issue needs to be triaged label Oct 10, 2024
@arendjr
Copy link
Contributor

arendjr commented Oct 10, 2024

This is a result of our lack of support for monorepos: #2228

@arendjr arendjr closed this as not planned Won't fix, can't repro, duplicate, stale Oct 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-Needs triage Status: this issue needs to be triaged
Projects
None yet
Development

No branches or pull requests

2 participants