Nested yml with remote config
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 19.7k
- Forks
- 2.3k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 11
Description
Hi guys,
We use a root .swiftlint.yml, and in the tests folder we have another .swiftlint.yml to disable some rules only in tests. Works great.
Now we are doing changes to have "universal ymls" for all our repos.
For that we changed the root yml to use a remote config and it works (located at './'):
parent_config: 'https://.../main/.swiftlint.yml'
But we can't get it to work for the nested yml for tests using a remote parent_config/child_config. It doesn't download the file into the cache.
Things we tried for the tests yml (located at './tests/'):
parent_config: 'https://.../main/.swiftlint.yml'
child_config: 'https://.../tests/.swiftlint.yml'
# or
parent_config: '../.swiftlint.yml'
child_config: 'https://.../tests/.swiftlint.yml'
# or
child_config: 'https://.../tests/.swiftlint.yml'
# or
parent_config: 'https://.../tests/.swiftlint.yml'
Using SwiftLint version 0.44.0.
Is there a way to achieve this? Thanks.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named in the issue. Start by reproducing the configuration using the root and tests/.swiftlint.yml files with remote parent_config and child_config values, then trace how nested configuration files are resolved and cached; done means the nested remote configuration is downloaded and applied correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100