Project-local config file
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.6k
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
efm-langserver could be a pretty handy tool for unifying project linting and formatting across developer machines and editors/IDEs. What prevents this from working easily is an option for project-local configuration files, where the project conventions can easily be enforced. Therefore, adding something like ${workspace_root}/.efm-config.yaml to the configuration cascade would be pretty handy. Otherwise, every developer has to explicitly instruct its IDE to launch with the project-local configuration file, which is more work and can be easily missed.
Contributor guide
No contributing guide indexed for this repository
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
Start by tracing efm-langserver’s existing configuration cascade and how it determines the workspace root. Define the expected precedence for a project-local .efm-config.yaml and add coverage showing that it is discovered; done means a workspace can use the file without IDE-specific launch arguments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100