1
1
Fork
You've already forked ecformat
0

Ignore files via EditorConfig property #58

Open
opened 2026年07月03日 07:40:08 +02:00 by BaumiCoder · 1 comment

Feature description

It should be possible to define inside .editorconfig files, which files should be ignored by ecformat. Maybe with a Boolean property named ecformat_ignore or similar.

Benefits

This would allow ignoring files without a separate ignore file (to use with --ignore-file) as pointed out in this Review comment.

Resources

  • Extensions of EditorConfig with custom properties
### Feature description It should be possible to define inside `.editorconfig` files, which files should be ignored by ecformat. Maybe with a Boolean property named `ecformat_ignore` or similar. ### Benefits This would allow ignoring files without a separate ignore file (to use with `--ignore-file`) as pointed out in [this Review comment](https://codeberg.org/silverpill/mitra/pulls/242#issuecomment-18454154). ### Resources - Extensions of EditorConfig with custom properties
Author
Owner
Copy link

One performance aspect should be considered for the implementation. Currently, ecformat take a look at the EditorConfig properties for each file. At this point it could check for such a new property ecformat_ignore and skip the file. However, this would imply that it iterates over all files of an ignored directory. This could impact the runtime performance in case of many files in there. Would it be possible to skip such directories without this overhead? How to handle cases that ecformat_ignore is true for a directory, but gets false via an .editorconfig in on of its subdirectories?

One performance aspect should be considered for the implementation. Currently, ecformat take a look at the EditorConfig properties for each file. At this point it could check for such a new property `ecformat_ignore` and skip the file. However, this would imply that it iterates over all files of an ignored directory. This could impact the runtime performance in case of many files in there. Would it be possible to skip such directories without this overhead? How to handle cases that `ecformat_ignore` is true for a directory, but gets false via an `.editorconfig` in on of its subdirectories?
Sign in to join this conversation.
No Branch/Tag specified
main
chore/dependencies-0.2.0
bugfix/47-subdirectory-sections-are-not-considered
enhancement/no-colors-log-to-file
bugfix/Too-many-open-files-via-ConfigFile
bugfix/spelling_language-unparsable-values
feature/38-status-command
chore/add-pre-commit-installation-to-issue-template
chore/add-crate-installation-to-issue-template
enhancement/finalize-0.17.2-editorconfig-support
feature/8-spelling_language
feature/7-indentation
bugfix/CI-change-detection
feature/6-insert_final_newline
feature/5-trim_trailing_whitespace
feature/16-pre-commit
chore/dependencies-0.1.1
chore/33-Make-CI-and-pre-commit-more-reproducable
bugfix/28-docs.rs-build
feature/31-support-multiple-target-files
chore/25-remove-reuse-workarounds
chore/dependencies-badge
feature/11-Rust-crate-on-crates.io
chore/10-CI
chore/9-licenses
feature/4-end_of_line
feature/2-linters
feature/3-charset
feature/18-log-levels
feature/1-ignore-files
v0.2.0
v0.1.1
v0.1.0
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
EditorConfig
0.17.2
Issues to support version 0.17.2 of the EditorConfig specification
Kind
Bug
Something is not working
Kind
Chore
Some tasks maintainig tasks
Kind
Documentation
Documentation changes
Kind
Enhancement
Improve existing functionality
Kind
Feature
New functionality
Kind
Testing
Issue or pull request related to testing
Packaging
About packaging the project for some platform
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
WIP
Work in progress (Assignee is working on this issue)
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
BaumiCoder/ecformat#58
Reference in a new issue
BaumiCoder/ecformat
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?