Flesh out description of poker exercise

Open
#2,153 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Domain
documentation

Research direction

Read the existing poker exercise description and compare it with exercises/yacht/description.md in the problem-specifications repository. Expand the poker description so it explains the applicable rules and does not rely on Wikipedia, including the special rules that this exercise ignores; done means the exercise can be understood offline.

Written by the indexing model from the issue text.

Description

The poker exercise currently only links to a wikipedia article for an explanation of the rules.
This is problematic in a couple of ways:

  • The wikipedia article mentions some special rules, which we ignore
  • If you don't have internet once you've downloaded the exercise, it is not easy to work on the exercise

I propose we do the same we did for yacht, another card game exercise, by fleshing out the description: https://github.com/exercism/problem-specifications/blob/main/exercises/yacht/description.md

Dominant language
Ruby
Stars
362
Forks
566
Avg merge
15h 13m
Merged PRs (30d)
8

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from exercism/problem-specifications

All issues in exercism/problem-specifications

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.