mgechev/revive

support build tags

Open

#230 opened on Sep 7, 2019

View on GitHubContributor guide
 (5 comments) (0 reactions) (0 assignees)Go (316 forks)github user discovery
feature requesthelp wanted

Repository metrics

Stars
 (5,517 stars)
PR merge metrics
 (Avg merge 10h 48m) (3 merged PRs in 30d)

Description

In order to lint all files, the linter needs to be able to use build tags. It will actually fail to run if all the files in a directory have build tags.

Contributor guide

Research direction
Investigate how revive loads and processes Go files, then modify the file loading logic to respect build tags by using the `go/build` package or similar to filter files based on build constraints.
Tech stack
go
Domain
tooling
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Go
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50