bazel-contrib / bazel-contrib/rules_go
nogo: idiomatic way to provide configuration file
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.5k
- Forks
- 762
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 12
Description
I'm playing with using nogo to write a simple spell checker. However, I'm trying to provide a custom per-project dictionary as a file, and I can't figure out how to pass it. My analyzer executes in a sandbox, so I can't just naively walk the directory tree. I can't figure out how to pass a data parameter to nogo, particularly because I want to scope it to one analyzer (that will eventually live in a different repo).
What is the right way to do this?
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
Start at the nogo entry point and trace how analyzer configuration and sandboxed data are passed, focusing on the requested data parameter and per-analyzer scope. There are no files or tests named in the issue; done means establishing an idiomatic configuration-file path that supports a project dictionary for one analyzer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100