react-bootstrap-table/react-bootstrap-table2

Use .eslint rules to keep code better organized

Open

#222 opened on Feb 21, 2018

View on GitHub
 (3 comments) (0 reactions) (0 assignees)JavaScript (1,249 stars) (415 forks)batch import
good first issue

Description

The code would be easier to read/contribute to if it was better organized.

Here are some rules that would really help the readibilty:

react/jsx-sort-props react/jsx-space-before-closing react/jsx-curly-spacing

Contributor guide

Tech stack
javascriptreact
Domain
frontenddeveloper experience
Issue type
chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
basic JavaScript knowledgefamiliarity with ESLintReact JSX syntax
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
Examine the repository's ESLint configuration file (likely .eslintrc or eslintConfig in package.json) to understand the current setup. Add the three specified rules (react/jsx sort props, react/jsx space before closing, react/jsx curly spacing) to the rules section. Run the linter to ensure no existing code is broken, and if needed, manually fix any violations. The issue's comments may provide additional context on preferred formatting.