Skip to content

Commit

Permalink
refactor: after review
Browse files Browse the repository at this point in the history
  • Loading branch information
PKulkoRaccoonGang committed Dec 10, 2024
1 parent 384dcdc commit df51d89
Show file tree
Hide file tree
Showing 3 changed files with 5 additions and 26 deletions.
6 changes: 0 additions & 6 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,12 +23,6 @@ Include `rg-frontend-linters` as a dependency:
}
```

Install the dependency:

```bash
npm install
```

### 2. Create a configuration file

Add a configuration file for the desired linter in the root of your project. For example, to configure Stylelint:
Expand Down
15 changes: 5 additions & 10 deletions RG_CHANGELOG.rst
Original file line number Diff line number Diff line change
Expand Up @@ -9,18 +9,13 @@ and this project adheres to customized Semantic Versioning e.g.: `redwood-rg.1`
[Unreleased]
************

[redwood-rg.3] 2024-11-28 (Redwood RG release)
2024-11-28
****************************************

Added:
=====
* add CI checkers: tests, linters checkers (RGInt-303)
* add configs and tests (RGInt-303)
* add documentation (RGInt-303)
* initialize project structure and add default configs (RGInt-303)

[redwood-rg.3] 2024-11-27 (Redwood RG release)
****************************************

Added:
=====
* initialize project structure (RGInt-303)
- add CI checkers: tests, linters checkers
- add configs and tests
- add documentation
10 changes: 0 additions & 10 deletions docs/decisions/0001-rg-frontend-linters.rst
Original file line number Diff line number Diff line change
@@ -1,16 +1,6 @@
Technical Solution Overview: RG Frontend Linters
================================================

RG Frontend Linters
|
|---> ESLint Config
|---> Stylelint Config
|---> CommitLint Config
| |
| |---> brand-openedx
| |---> frontend-component-header
| |---> frontend-component-footer
**RG Frontend Linters** is a solution designed to standardize configurations for **ESLint**, **Stylelint**, and **CommitLint**,
ensuring consistent code quality, styling, and commit message validation across projects. By abstracting the configuration logic into reusable modules,
this approach streamlines the integration process for developers, reduces onboarding time, and enforces consistent standards across teams and projects.
Expand Down

0 comments on commit df51d89

Please sign in to comment.