Skip to content
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

Update sport docs #2687

Closed
wants to merge 2 commits into from
Closed

Update sport docs #2687

wants to merge 2 commits into from

Conversation

clementf
Copy link
Contributor

Summary

This PR contains only a documentation change. I've noticed recently while using faker that all the examples in the docs for the Faker::Sport class contain a typo (they have an additional s in the class name).

PS: thank you for creating, and maintaining this ruby gem, which I've been using in a lot of projects!

Copy link
Contributor

@stefannibrasil stefannibrasil left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thank you @clementf good catch!

Have you considered also updating the test file? It's also using Faker::Sports.

@stefannibrasil
Copy link
Contributor

Closing this as there has not been activity for the past 2 weeks. Feel free to reopen anytime. Thanks!

@clementf
Copy link
Contributor Author

@stefannibrasil thank you for the feedback; and apologies for the delayed reply.

When you say updating the test file, do you mean turning TestFakerSports into TestFakerSport and updating the filename accordingly?

@stefannibrasil
Copy link
Contributor

@clementf no worries, thanks for the interest in helping out! Yes, you're right. Since we are updating the generator, it's important to update the tests as well. Thank you!

@clementf
Copy link
Contributor Author

@stefannibrasil you're right indeed, I had overlooked those test files. I made the necessary changes, could you reopen the PR?

@stefannibrasil
Copy link
Contributor

stefannibrasil commented Feb 20, 2023

@clementf thank you! I can't reopen it because it says this branch has been force-pushed or recreated. I also didn't see the test changes in this PR. Maybe there is another branch that does not an open PR yet? If so, feel free to open a new PR and mention this PR on the description. Thanks!

@clementf clementf mentioned this pull request Feb 21, 2023
@clementf
Copy link
Contributor Author

@stefannibrasil I did rebase to include the changes from the main branch, I'm guessing this is the reason. I've opened another PR at #2716
Sorry for the back and forth!

@stefannibrasil
Copy link
Contributor

all good, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants