-
-
Notifications
You must be signed in to change notification settings - Fork 531
Autogenerate README based on description.md #721
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,5 +1,3 @@ | ||
| # Acronym | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why have all the titles disappeared?
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The titles disappeared because the original problem-specfications/description.md don't have it in them. Accumulate README from problem-specfications: Ruby's Accumulate README: I was thinking about adding the titles into the description.md of problem-specifications for every problem so that when generator gets run the titles don't disappear.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Please have a read through this thread an the associated issues/PRs:
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. And: https://github.com/Insti/trackler/blob/master/lib/trackler/implementation.rb#L87
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Things are a bit more complicated than normal right now as we're trying to make sure that the exercises are compatible with both the existing exercism.io site and the new https://v2.exercism.io/ (nextercism) site that have slightly different requirements. |
||
|
|
||
| Convert a phrase to its acronym. | ||
|
|
||
| Techies love their TLA (Three Letter Acronyms)! | ||
|
|
@@ -32,10 +30,5 @@ To include color from the command line: | |
|
|
||
| ruby -r minitest/pride hello_world_test.rb | ||
|
|
||
|
|
||
| ## Source | ||
|
|
||
| Julien Vanier [https://github.com/monkbroc](https://github.com/monkbroc) | ||
|
|
||
| ## Submitting Incomplete Solutions | ||
| It's possible to submit an incomplete solution so you can see how others have completed the exercise. | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,42 @@ | ||
| Correctly determine the fewest number of coins to be given to a customer such | ||
| that the sum of the coins' value would equal the correct amount of change. | ||
|
|
||
| ## For example | ||
|
|
||
| - An input of 15 with [1, 5, 10, 25, 100] should return one nickel (5) | ||
| and one dime (10) or [0, 1, 1, 0, 0] | ||
| - An input of 40 with [1, 5, 10, 25, 100] should return one nickel (5) | ||
| and one dime (10) and one quarter (25) or [0, 1, 1, 1, 0] | ||
|
|
||
| ## Edge cases | ||
|
|
||
| - Does your algorithm work for any given set of coins? | ||
| - Can you ask for negative change? | ||
| - Can you ask for a change value smaller than the smallest coin value? | ||
|
|
||
| * * * * | ||
|
|
||
| For installation and learning resources, refer to the | ||
| [exercism help page](http://exercism.io/languages/ruby). | ||
|
|
||
| For running the tests provided, you will need the Minitest gem. Open a | ||
| terminal window and run the following command to install minitest: | ||
|
|
||
| gem install minitest | ||
|
|
||
| If you would like color output, you can `require 'minitest/pride'` in | ||
| the test file, or note the alternative instruction, below, for running | ||
| the test file. | ||
|
|
||
| In order to run the test, you can run the test file from the exercise | ||
| directory. For example, if the test suite is called | ||
| `hello_world_test.rb`, you can run the following command: | ||
|
|
||
| ruby hello_world_test.rb | ||
|
|
||
| To include color from the command line: | ||
|
|
||
| ruby -r minitest/pride hello_world_test.rb | ||
|
|
||
| ## Submitting Incomplete Solutions | ||
| It's possible to submit an incomplete solution so you can see how others have completed the exercise. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
docs:is not an appropriate argument here, the docs path should be derived from thetrack: EXERCISM_RUBY_ROOT