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

Docs: formatting of the compatibility section #10737

Closed
wants to merge 1 commit into from
Closed

Docs: formatting of the compatibility section #10737

wants to merge 1 commit into from

Conversation

pkuczynski
Copy link
Contributor

What is the purpose of this pull request? (put an "X" next to item)

[X] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofixing to a rule
[ ] Add a CLI option
[ ] Add something to the core
[ ] Other, please explain:

What changes did you make? (Give an overview)

Formatted Compatibility section to match changes proposed in #10736

Is there anything you'd like reviewers to focus on?

Nope.

@eslint-deprecated eslint-deprecated bot added the triage An ESLint team member will look at this issue soon label Aug 6, 2018
@platinumazure
Copy link
Member

I like the intent of this change, but I think we were considering trying to use a different JSCS site as a link target for the JSCS rule names, rather than completely remove the domain names. So I guess I see this as on hold until we figure out the JSCS hyperlink situation.

@kaicataldo
Copy link
Member

Closing as per the author's comment here

@kaicataldo kaicataldo closed this Oct 15, 2018
@eslint-deprecated eslint-deprecated bot locked and limited conversation to collaborators Apr 14, 2019
@eslint-deprecated eslint-deprecated bot added the archived due to age This issue has been archived; please open a new issue for any further discussion label Apr 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
archived due to age This issue has been archived; please open a new issue for any further discussion triage An ESLint team member will look at this issue soon
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants