-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Modify email method in Internet class #1259
Conversation
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.
Could you update the changelog
and take a look at the comment that I wrote?
[user_name(name, separators), domain_name].join('@') | ||
else | ||
[user_name(name), domain_name].join('@') | ||
end |
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.
I think you should create two tests because you have two scenarios.
I added a new rake task. I don't know if I told you: rake coverage_report
. By running this command, you can see the code coverage report.
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.
There was a test already in place to test the else
case. I only added the first scenario, which is why only one test was needed. Also, running rake coverage_report
opens up a page in my browser and shoes me coverage report. I don't get a report on the terminal. Is this how it's supposed to work?
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.
I didn't see the test for the else
statement. Let me check it out.
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.
doh it's correct 👍 sorry about that
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.
Overall looks good 🥇
Faker::Internet.email #=> "[email protected]" | ||
|
||
Faker::Internet.email('Nancy') #=> "[email protected]" | ||
|
||
Faker::Internet.email('Janelle Santiago', '+') #=> [email protected]" | ||
|
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.
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.
I wonder if these are Google's specific restrictions. It looks like this is a larger topic than I expected. And from stack overflow.
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.
I say skip the whitelist... if people are using the optional argument to add separators, then it's up to them to wield the sharp knife safely. :)
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.
yeah if we don't do that, we could focus on other features and bugs
* Modify email method in Internet class * Update CHANGELOG.md
This PR is for the feature request in issue #1178.
The PR does: