Recursion Exercises: Add new factorial exercise #98
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Because
We want to bring the recursion exercises done in the recursion lesson in house.
Link the curriculum issue for this: TheOdinProject/curriculum#27265 (comment)
This PR
Issue
Closes #XXXXX
Additional Information
Leaving this as a draft for the time being. The main question I'd have is: are we okay with this organization / structure, or do we want to approach this differently?
Currently all the exercises in this repo are for "basic ruby." It might make sense to create an entirely new repo for these new exercises, which is the same way we do the custom enumerables project.
If we do leave them in this repo, is the way I have them organized here okay? Definitely interested in other maintainer input on the approach here.
Pull Request Requirements
location of change: brief description of change
format, e.g.Data types exercise: Update spec files
Because
section summarizes the reason for this PRThis PR
section has a bullet point list describing the changes in this PRsolutions
branch, I have created another PR (and linked it to this PR).