Skip to content

chore: fix EditorConfig lint errors - #15099

Merged
kgryte merged 1 commit into
stdlib-js:developfrom
dchaudhari7177:fix-editorconfig-15088
Sep 10, 2026
Merged

chore: fix EditorConfig lint errors#15099
kgryte merged 1 commit into
stdlib-js:developfrom
dchaudhari7177:fix-editorconfig-15088

Conversation

@dchaudhari7177

Copy link
Copy Markdown
Contributor

Resolves #15088.

Description

This pull request:

  • re-indents lines 39–51 of lib/node_modules/@stdlib/_tools/eslint/rules/no-builtin-math/examples/index.js with tabs instead of spaces.

The /* => ... */ example-output block used 4-space indentation, while .editorconfig sets indent_style = tab for [*.{js,js.txt}]. Each level is replaced by one tab at the same depth (4→1, 8→2, 12→3), so the rendered block is unchanged in structure.

Verified with editorconfig-checker against the repository's own .editorconfig:

BEFORE  before.js:
          39-51: wrong indentation type (spaces instead of tabs)
        1 errors found

AFTER   (no output, exit 0)

That matches the workflow error in the issue exactly. I also confirmed the change is whitespace-only: diff <(tr -d ' \t' < before.js) <(tr -d ' \t' < after.js) is empty.

Related Issues

This pull request has the following related issues:

Questions

No.

Other

No.

Checklist

AI Assistance

When authoring the changes proposed in this PR, did you use any kind of AI assistance?

  • Yes
  • No

If you answered "yes" above, how did you use AI assistance?

  • Code generation (e.g., when writing an implementation or fixing a bug)
  • Test/benchmark generation
  • Documentation (including examples)
  • Research and understanding

I used an AI assistant to locate the flagged lines and apply the re-indentation, then verified the result myself by running editorconfig-checker against the repository's .editorconfig on both the original and the patched file, and by confirming the diff is whitespace-only.

The '/* => ... */' example output block was indented with spaces while
.editorconfig sets indent_style = tab for *.js, so the EditorConfig lint
job failed on lines 39-51. Re-indent those lines with tabs at the same
depth. Indentation only; no other bytes change.
@dchaudhari7177
dchaudhari7177 requested a review from a team September 8, 2026 06:52
@stdlib-bot stdlib-bot added Tools Issue or pull request related to project tooling. Needs Review A pull request which needs code review. Good First PR A pull request resolving a Good First Issue. Potential Duplicate There might be another pull request resolving the same issue. labels Sep 8, 2026
@kgryte kgryte added difficulty: 1 Low degree of difficulty. Should be straightforward to implement and/or resolve. review: 5 and removed Needs Review A pull request which needs code review. labels Sep 10, 2026
@kgryte kgryte changed the title chore: fix EditorConfig lint errors (issue #15088) chore: fix EditorConfig lint errors Sep 10, 2026
@kgryte
kgryte merged commit d30d365 into stdlib-js:develop Sep 10, 2026
112 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

difficulty: 1 Low degree of difficulty. Should be straightforward to implement and/or resolve. Good First PR A pull request resolving a Good First Issue. Potential Duplicate There might be another pull request resolving the same issue. review: 5 Tools Issue or pull request related to project tooling.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fix EditorConfig lint errors

3 participants