allow specifying custom build tags
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 692
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
wire relies on custom build tags in initializer files to generate code. The files that are loaded/built by default are part of the generated output and the files that rf should really be refactoring are not built unless the wireinject built tag is set. There should be a way to tell rf to use this build tag when loading and refactoring code.
There may be a larger question of how to refactor every version of code that relies heavily on build tags, but I don't want to open that can of worms. I hope it's simple enough to specify a single set of tags to use when loading/refactoring code.
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 rf's loading and refactoring entry points to find where build tags are selected. Add a way to supply one set of custom tags, then verify that files requiring those tags are loaded and refactored while default loading remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100