chore: fix EditorConfig lint errors (issue #15088) - #15099
Open
dchaudhari7177 wants to merge 1 commit into
Open
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolves #15088.
Description
This pull request:
lib/node_modules/@stdlib/_tools/eslint/rules/no-builtin-math/examples/index.jswith tabs instead of spaces.The
/* => ... */example-output block used 4-space indentation, while.editorconfigsetsindent_style = tabfor[*.{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-checkeragainst the repository's own.editorconfig: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
If you answered "yes" above, how did you use AI assistance?
I used an AI assistant to locate the flagged lines and apply the re-indentation, then verified the result myself by running
editorconfig-checkeragainst the repository's.editorconfigon both the original and the patched file, and by confirming the diff is whitespace-only.