Skip to content

feat(linter): Add a warning when Oxlint is used without a configuration file.#19313

Open
cpojer wants to merge 1 commit intooxc-project:mainfrom
cpojer:default-lint-warning
Open

feat(linter): Add a warning when Oxlint is used without a configuration file.#19313
cpojer wants to merge 1 commit intooxc-project:mainfrom
cpojer:default-lint-warning

Conversation

@cpojer
Copy link
Copy Markdown
Contributor

@cpojer cpojer commented Feb 12, 2026

Prompt:

When oxlint doesn't find any config, it runs with defaults. Can you add a yellow note text (use a helper if it already exists in the repo for notes, otherwise inline it) saying: "Using Oxlint's default configuration. Run oxlint --init to set up Oxlint in this project."

Codex GPT 5.3 xhigh

@cpojer cpojer requested a review from camc314 as a code owner February 12, 2026 09:17
Copilot AI review requested due to automatic review settings February 12, 2026 09:17
@github-actions github-actions bot added A-linter Area - Linter A-cli Area - CLI labels Feb 12, 2026
@cpojer cpojer changed the title Add a warning when Oxlint is used without a configuration file. feat: Add a warning when Oxlint is used without a configuration file. Feb 12, 2026
@cpojer cpojer changed the title feat: Add a warning when Oxlint is used without a configuration file. feat(linter): Add a warning when Oxlint is used without a configuration file. Feb 12, 2026
@github-actions github-actions bot added the C-enhancement Category - New feature or request label Feb 12, 2026
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a user-facing warning when oxlint runs without discovering any configuration, helping users understand they’re linting with defaults and how to initialize a project config.

Changes:

  • Emit a yellow “default configuration” note when no root config, no nested configs, and no --config are present.
  • Route the note to stderr by plumbing an internal run_with_stderr entrypoint.
  • Add unit tests covering both “no config found” and “auto config found” cases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-cli Area - CLI A-linter Area - Linter C-enhancement Category - New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants