mgechev/revive

Add go version information for each rule in documentation

Open

#1,311 opened on Apr 10, 2025

View on GitHubContributor guide
 (7 comments) (0 reactions) (0 assignees)Go (316 forks)github user discovery
docsgood first issue

Repository metrics

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

Description

one interesting thing could be to add a column to this table to mention the Go version specification

Something like < 1.23 here, and > 1.18 for use-any, and others.

Originally posted by @ccoVeille in https://github.com/mgechev/revive/pull/1273#discussion_r1997659854

This comment was provided when reviewing a PR about a new linter

Contributor guide

Research direction
Identify the documentation table listing rules and add a column indicating the Go version requirement for each rule. Check existing rule files for version constraints.
Tech stack
go
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
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
GitGo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90