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

Add rule to check if opener was disowned #174

Merged
merged 1 commit into from
May 2, 2017
Merged

Add rule to check if opener was disowned #174

merged 1 commit into from
May 2, 2017

Conversation

alrra
Copy link
Contributor

@alrra alrra commented May 2, 2017

Fix #149

@alrra alrra requested review from molant and sarvaje May 2, 2017 17:37
* The reason why the rule does not check the same origin links by
default is because:

* security isn't really a problem here
Copy link
Member

Choose a reason for hiding this comment

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

Missing trailing .

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed.

</map>
</body>
</html>`
```
Copy link
Member

Choose a reason for hiding this comment

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

Maybe add here that this rule will be triggered only one by <a href="http://example2.com" target="_blank">test</a> ?

Copy link
Contributor Author

@alrra alrra May 2, 2017

Choose a reason for hiding this comment

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

I've updated the examples. Let me know what you think.


const ruleName = getRuleName(__dirname);

const generateHTML = (body: string): string => {
Copy link
Member

Choose a reason for hiding this comment

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

Should we put this as a helper for all rules and accept head and body (with empty strings as defaults)?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Will do that as part of #162.

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