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

Tells users how to handle uninitialized constant error #995

Merged
merged 3 commits into from
Sep 2, 2017

Conversation

jwpincus
Copy link
Contributor

updates readme to explain to users how to fix common uninitialized constant error

README.md Outdated
@@ -116,6 +116,11 @@ Contents
```bash
gem install faker
```
Note: if you are getting a `uninitialized constant Faker::[some_class]` error, your version of the gem is behind the one documented here. To make sure that your gem is the most up to date, change the line in your gemfile to:

```bash
Copy link
Contributor

Choose a reason for hiding this comment

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

this is ruby and not bash

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good catch. Has been fixed, with added nuance.

@stympy stympy merged commit dfb0762 into faker-ruby:master Sep 2, 2017
@jwpincus jwpincus deleted the patch-1 branch September 8, 2017 21:52
landongrindheim pushed a commit to landongrindheim/faker that referenced this pull request Oct 7, 2017
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.

3 participants