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.

Sign up for GitHub

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

Jump to bottom

Document nested configuration merge rules #2856

Open
jpsim opened this issue Sep 3, 2019 · 1 comment
Open

Document nested configuration merge rules #2856

jpsim opened this issue Sep 3, 2019 · 1 comment
Labels
good first issue Issue to be taken up by new contributors yet unfamiliar with the project.

Comments

@jpsim
Copy link
Collaborator

jpsim commented Sep 3, 2019

User @AnthonyMDev commented in #1674 about the lack of documentation around how SwiftLint merges nested configuration files. We should document the rules involved in config merging, either in our readme or a separate doc file.

This is a great possible "starter ticket" for users of SwiftLint that would like to contribute (😉 @AnthonyMDev). Looking at Configuration+Merging.swift and ConfigurationTests+Nested.swift would be a good place to start to understand the logic involved.
@jpsim jpsim added the good first issue Issue to be taken up by new contributors yet unfamiliar with the project. label Sep 3, 2019
@jpsim jpsim mentioned this issue Sep 3, 2019
Closed
@stale
Copy link

stale bot commented Nov 8, 2020

This issue has been automatically marked as stale because it has not had any recent activity. Please comment to prevent this issue from being closed. Thank you for your contributions!

@stale stale bot added the wontfix Issues that became stale and were auto-closed by a bot. label Nov 8, 2020
@stale stale bot closed this as completed Nov 15, 2020
@jpsim jpsim reopened this Feb 23, 2021
@jpsim jpsim removed the wontfix Issues that became stale and were auto-closed by a bot. label Feb 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Issue to be taken up by new contributors yet unfamiliar with the project.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jpsim