Append Ruby leap instructions to instruct user not use Date class

I created a PR to append the Ruby leap exercise instructions based on the comments on this issue.

1 Like

I have added a comment that should direct you to create an append file where we can have more specific information for the Ruby track, and the upstream information will not overwrite this when this exercise is maintained.

Let’s state clearly that it is the Date class’s leap? method that we can or should avoid. No reason to make the student have to go looking for it.

I have also added a link back to this discussion from the pull request to help keep the connections intact.

1 Like

The pull request is merged, and we should see it in place when the hamsters get their exercise.

2 Likes