p0deje/yard-doctest

Thank you!

Open

#15 opened on Oct 6, 2020

View on GitHubContributor guide
 (1 comment) (0 reactions) (0 assignees)Gherkin (17 forks)github user discovery
help wantedquestion

Repository metrics

Stars
 (117 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Hi @p0deje, this is not an issue exactly. I just wanted to thank you (and any other contributors) for the yard-doctest gem, which has worked super easily and smoothly for me.

It's so valuable to have test coverage of documentation code examples. I'd love to see this practice more publicized, perhaps through a blog post picked up on Ruby Weekly News?

Thanks again, -Marc

Contributor guide

Research direction
Acknowledge the thanks and consider closing the issue as it is not a bug or feature request. If desired, create a discussion to encourage blog posts.
Tech stack
ruby
Domain
testing
Issue type
Documentation
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.
Under 1 hour
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
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90