You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Part of epic R1 · Public repos that wow (linked as parent issue).
Rescoped 2026-11-21 to the provider / source layout (I19): kinds/<kind>/ is how a source is read, providers/<provider>/ is what is read. A reference is a provider folder, not a plugin.
Story
As a contributor, I want one small, well-commented reference provider for each kind, so I can copy the right example instead of reading a large real one.
Subtasks
For each kind under kinds/, pick (or trim) one existing provider folder under providers/ whose source of that kind is short and clear
Comment every step in that provider's provider.go (and its <source>.go, if any) and its README's Why this source section
Each reference has its tests and a small testdata/ sample
new-plugin uses the reference for the chosen kind as its base
Link each kind's reference from docs/which-kind.md (no separate list anywhere else)
Acceptance criteria
Every kind has exactly one reference provider, linked from docs/which-kind.md
Each reference is short enough to read in a few minutes and its tests pass
new-plugin output matches the reference for its kind
Retitled and rescoped (approved 2026-11-21): with the kinds/ + providers/<provider>/ layout, the reference is one exemplary provider folder per kind, linked from docs/which-kind.md. No marking in a plugin list (there is none).
Activity
[-]R1.6 · One reference plugin per format[/-][+]R1.6 · One reference provider per kind[/+]adssib commentedon Nov 21, 2026
Retitled and rescoped (approved 2026-11-21): with the
kinds/+providers/<provider>/layout, the reference is one exemplary provider folder per kind, linked fromdocs/which-kind.md. No marking in a plugin list (there is none).