Fix EditorConfig lint errors #15088 - #15134
Conversation
Signed-off-by: Rajdeep <palr73414@gmail.com>
|
Hello! Thank you for your contribution to stdlib. We noticed that the contributing guidelines acknowledgment is missing from your pull request. Here's what you need to do:
This acknowledgment confirms that you've read the guidelines, which include:
We can't review or accept contributions without this acknowledgment. Thank you for your understanding and cooperation. We look forward to reviewing your contribution! |
Signed-off-by: Rajdeep <palr73414@gmail.com>
|
Hello! Thank you for your contribution to stdlib. We noticed that the contributing guidelines acknowledgment is missing from your pull request. Here's what you need to do:
This acknowledgment confirms that you've read the guidelines, which include:
We can't review or accept contributions without this acknowledgment. Thank you for your understanding and cooperation. We look forward to reviewing your contribution! |
Resolves #15088.
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:
#15088
Questions
No.
Other
No.
Checklist
Read, understood, and followed the contributing guidelines.
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.