-
Notifications
You must be signed in to change notification settings - Fork 0
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
Closes #17; Better Domain Filtering #18
Conversation
@tjmehta - Please review. |
it looks like your branch has duplicates of commits that are now on master... maybe rebase? |
Just needed to merge them in. Sorry about that. |
return names.filter(function (name) { | ||
return ~name.indexOf(process.env.DOMAIN_FILTER); | ||
return name.match(regexFilter); |
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.
it looks like you're filtering and allowing anything on a domain (good), but then looking for 0-infinite whitespace after before the end of the line? why not just trim
?
]; | ||
query.resolve('127.0.0.1', names, function (err, records) { | ||
if (err) { return done(err); } | ||
expect(records).to.be.null(); |
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.
to help prevent this, add -a code
to the lab
command - it'll throw errors if not all the expect(...)
s are resolved
if you want to update the |
Closes #17; Better Domain Filtering
Use a regex to ensure that the domain filter appears at the end of the domain instead of anywhere.