Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GH-19 clarified leading slash in the spec #68

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

mipo256
Copy link
Contributor

@mipo256 mipo256 commented Jan 14, 2025

Resolves #19


📚 Documentation preview 📚: https://editorconfig-specification--68.org.readthedocs.build/

@mipo256 mipo256 changed the title GH-19 clarified laeding slash in the spec GH-19 clarified leading slash in the spec Jan 14, 2025
@xuhdev
Copy link
Member

xuhdev commented Jan 15, 2025

I think this is good clarification, but we still need to ensure our tests have covered this case

Copy link
Member

@cxw42 cxw42 left a comment

Choose a reason for hiding this comment

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

@mipo256 thanks for the PR! Have you run modified core tests covering this case, as suggested by @xuhdev ? If you could open a corresponding PR in https://github.com/editorconfig/editorconfig-core-test , that would add confidence in this change.

Other than testing, I have one request for a modification to the text.

level. For example, ``*.c`` matches any file that ends with ``.c`` in the
level.

Therefore, similar to a `gitignore format`_, a leading slash is not relevant if there is already a slash in the middle of the pattern.
Copy link
Member

Choose a reason for hiding this comment

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

I don't think we should mention gitignore here, lest people think that editorconfig files have the same semantics as gitignore files.

Suggested change
Therefore, similar to a `gitignore format`_, a leading slash is not relevant if there is already a slash in the middle of the pattern.
Therefore, a leading slash is not relevant if there is already a slash in the middle of the pattern.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Clarify the behavior of leading slash in section title
3 participants