Skip to content

Commit 96b3b06

Browse files
committed
[meta] reflect the repo rename; remove travis badge
1 parent e52eed5 commit 96b3b06

24 files changed

+1377
-1380
lines changed

.github/workflows/smoke-test.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ on:
77

88
jobs:
99
smoke-test:
10-
if: ${{ github.repository == 'yannickcr/eslint-plugin-react' || github.event_name == 'workflow_dispatch' }}
10+
if: ${{ github.repository == 'jsx-eslint/eslint-plugin-react' || github.event_name == 'workflow_dispatch' }}
1111
runs-on: ubuntu-latest
1212
steps:
1313
- uses: actions/checkout@v2

CHANGELOG.md

Lines changed: 1342 additions & 1342 deletions
Large diffs are not rendered by default.

README.md

Lines changed: 9 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
`eslint-plugin-react`
22
===================
33

4-
[![Maintenance Status][status-image]][status-url] [![NPM version][npm-image]][npm-url] [![Build Status][travis-image]][travis-url] [![Dependency Status][deps-image]][deps-url] [![Code Climate][climate-image]][climate-url] [![Tidelift][tidelift-image]][tidelift-url]
4+
[![Maintenance Status][status-image]][status-url] [![NPM version][npm-image]][npm-url] [![Dependency Status][deps-image]][deps-url] [![Code Climate][climate-image]][climate-url] [![Tidelift][tidelift-image]][tidelift-url]
55

66
React specific linting rules for `eslint`
77

@@ -25,7 +25,7 @@ Use [our preset](#recommended) to get reasonable defaults:
2525
]
2626
```
2727

28-
If you are using the [new JSX transform from React 17](https://reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html#removing-unused-react-imports), extend [`react/jsx-runtime`](https://github.com/yannickcr/eslint-plugin-react/blob/c8917b0885094b5e4cc2a6f613f7fb6f16fe932e/index.js#L163-L176) in your eslint config (add `"plugin:react/jsx-runtime"` to `"extends"`) to disable the relevant rules.
28+
If you are using the [new JSX transform from React 17](https://reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html#removing-unused-react-imports), extend [`react/jsx-runtime`](https://github.com/jsx-eslint/eslint-plugin-react/blob/c8917b0885094b5e4cc2a6f613f7fb6f16fe932e/index.js#L163-L176) in your eslint config (add `"plugin:react/jsx-runtime"` to `"extends"`) to disable the relevant rules.
2929

3030
You should also specify settings that will be shared across all the plugin rules. ([More about eslint shared settings](https://eslint.org/docs/user-guide/configuring/configuration-files#adding-shared-settings))
3131

@@ -266,17 +266,14 @@ This pairs well with the `eslint:all` rule.
266266
[npm-url]: https://npmjs.org/package/eslint-plugin-react
267267
[npm-image]: https://img.shields.io/npm/v/eslint-plugin-react.svg
268268

269-
[travis-url]: https://travis-ci.org/yannickcr/eslint-plugin-react
270-
[travis-image]: https://img.shields.io/travis/yannickcr/eslint-plugin-react/master.svg
269+
[deps-url]: https://david-dm.org/jsx-eslint/eslint-plugin-react
270+
[deps-image]: https://img.shields.io/david/dev/jsx-eslint/eslint-plugin-react.svg
271271

272-
[deps-url]: https://david-dm.org/yannickcr/eslint-plugin-react
273-
[deps-image]: https://img.shields.io/david/dev/yannickcr/eslint-plugin-react.svg
272+
[climate-url]: https://codeclimate.com/github/jsx-eslint/eslint-plugin-react
273+
[climate-image]: https://img.shields.io/codeclimate/maintainability/jsx-eslint/eslint-plugin-react.svg
274274

275-
[climate-url]: https://codeclimate.com/github/yannickcr/eslint-plugin-react
276-
[climate-image]: https://img.shields.io/codeclimate/maintainability/yannickcr/eslint-plugin-react.svg
277-
278-
[status-url]: https://github.com/yannickcr/eslint-plugin-react/pulse
279-
[status-image]: https://img.shields.io/github/last-commit/yannickcr/eslint-plugin-react.svg
275+
[status-url]: https://github.com/jsx-eslint/eslint-plugin-react/pulse
276+
[status-image]: https://img.shields.io/github/last-commit/jsx-eslint/eslint-plugin-react.svg
280277

281278
[tidelift-url]: https://tidelift.com/subscription/pkg/npm-eslint-plugin-react?utm_source=npm-eslint-plugin-react&utm_medium=referral&utm_campaign=readme
282-
[tidelift-image]: https://tidelift.com/badges/github/yannickcr/eslint-plugin-react?style=flat
279+
[tidelift-image]: https://tidelift.com/badges/github/jsx-eslint/eslint-plugin-react?style=flat

docs/rules/jsx-no-target-blank.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -99,7 +99,7 @@ var Hello = <a target='_blank' href="https://example.com/"></form>
9999

100100
### Custom link components
101101

102-
This rule supports the ability to use custom components for links, such as `<Link />` which is popular in libraries like `react-router`, `next.js` and `gatsby`. To enable this, define your custom link components in the global [shared settings](https://github.com/yannickcr/eslint-plugin-react/blob/master/README.md#configuration) under the `linkComponents` configuration area. Once configured, this rule will check those components as if they were `<a />` elements.
102+
This rule supports the ability to use custom components for links, such as `<Link />` which is popular in libraries like `react-router`, `next.js` and `gatsby`. To enable this, define your custom link components in the global [shared settings](https://github.com/jsx-eslint/eslint-plugin-react/blob/master/README.md#configuration) under the `linkComponents` configuration area. Once configured, this rule will check those components as if they were `<a />` elements.
103103

104104
Examples of **incorrect** code for this rule:
105105

@@ -119,7 +119,7 @@ var Hello = <Link />
119119

120120
### Custom form components
121121

122-
This rule supports the ability to use custom components for forms. To enable this, define your custom form components in the global [shared settings](https://github.com/yannickcr/eslint-plugin-react/blob/master/README.md#configuration) under the `formComponents` configuration area. Once configured, this rule will check those components as if they were `<form />` elements.
122+
This rule supports the ability to use custom components for forms. To enable this, define your custom form components in the global [shared settings](https://github.com/jsx-eslint/eslint-plugin-react/blob/master/README.md#configuration) under the `formComponents` configuration area. Once configured, this rule will check those components as if they were `<form />` elements.
123123

124124
## When To Override It
125125

docs/rules/jsx-space-before-closing.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Validate spacing before closing bracket in JSX (react/jsx-space-before-closing)
22

3-
**Deprecation notice**: This rule is deprecated. Please use the `"beforeSelfClosing"` option of the [jsx-tag-spacing](https://github.com/yannickcr/eslint-plugin-react/blob/master/docs/rules/jsx-tag-spacing.md) rule instead.
3+
**Deprecation notice**: This rule is deprecated. Please use the `"beforeSelfClosing"` option of the [jsx-tag-spacing](https://github.com/jsx-eslint/eslint-plugin-react/blob/master/docs/rules/jsx-tag-spacing.md) rule instead.
44

55
Enforce or forbid spaces before the closing bracket of self-closing JSX elements.
66

docs/rules/jsx-uses-react.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,4 +45,4 @@ var Hello = <div>Hello {this.props.name}</div>;
4545

4646
If you are not using JSX, if React is declared as global variable, or if you do not use the `no-unused-vars` rule.
4747

48-
If you are using the [new JSX transform from React 17](https://reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html#removing-unused-react-imports), you should disable this rule by extending [`react/jsx-runtime`](https://github.com/yannickcr/eslint-plugin-react/blob/HEAD/index.js#L163-L176) in your eslint config (add `"plugin:react/jsx-runtime"` to `"extends"`).
48+
If you are using the [new JSX transform from React 17](https://reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html#removing-unused-react-imports), you should disable this rule by extending [`react/jsx-runtime`](https://github.com/jsx-eslint/eslint-plugin-react/blob/HEAD/index.js#L163-L176) in your eslint config (add `"plugin:react/jsx-runtime"` to `"extends"`).

docs/rules/no-array-index-key.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -106,4 +106,4 @@ things.reduceRight((collection, thing) => (
106106

107107
## When Not To Use It
108108

109-
If there is nothing unique about the items, for example [you are breaking an array down in to chunks](https://github.com/yannickcr/eslint-plugin-react/issues/1123), then you may want to disable this rule with an override.
109+
If there is nothing unique about the items, for example [you are breaking an array down in to chunks](https://github.com/jsx-eslint/eslint-plugin-react/issues/1123), then you may want to disable this rule with an override.

docs/rules/no-find-dom-node.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
Facebook will eventually deprecate `findDOMNode` as it blocks certain improvements in React in the future.
44

5-
It is recommended to use callback refs instead. See [Dan Abramov comments and examples](https://github.com/yannickcr/eslint-plugin-react/issues/678#issue-165177220).
5+
It is recommended to use callback refs instead. See [Dan Abramov comments and examples](https://github.com/jsx-eslint/eslint-plugin-react/issues/678#issue-165177220).
66

77
## Rule Details
88

docs/rules/prefer-stateless-function.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ This rule will check your class based React components for
1111
* extension of `React.PureComponent` (if the `ignorePureComponents` flag is true)
1212
* presence of `ref` attribute in JSX
1313
* the use of decorators
14-
* `render` method that return anything but JSX: `undefined`, `null`, etc. (only in React <15.0.0, see [shared settings](https://github.com/yannickcr/eslint-plugin-react/blob/master/README.md#configuration) for React version configuration)
14+
* `render` method that return anything but JSX: `undefined`, `null`, etc. (only in React <15.0.0, see [shared settings](https://github.com/jsx-eslint/eslint-plugin-react/blob/master/README.md#configuration) for React version configuration)
1515

1616
If none of these elements are found, the rule will warn you to write this component as a pure function.
1717

docs/rules/prop-types.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -153,7 +153,7 @@ It would seem that some common properties such as `props.children` or `props.cla
153153
(and alike) need to be treated as exceptions.
154154

155155
As it aptly noticed in
156-
[#7](https://github.com/yannickcr/eslint-plugin-react/issues/7)
156+
[#7](https://github.com/jsx-eslint/eslint-plugin-react/issues/7)
157157

158158
> Why should children be an exception?
159159
> Most components don't need `this.props.children`, so that makes it extra important

0 commit comments

Comments
 (0)