Skip to content

Commit

Permalink
Merge branch 'main' of github.com:zengxiaoluan/eslint-plugin-jlc
Browse files Browse the repository at this point in the history
  • Loading branch information
zengxiaoluan committed Jul 29, 2024
2 parents 4d745e5 + c4ea1c8 commit 05a8181
Show file tree
Hide file tree
Showing 2 changed files with 36 additions and 6 deletions.
31 changes: 31 additions & 0 deletions .github/workflows/node.js.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
# This workflow will do a clean installation of node dependencies, cache/restore them, build the source code and run tests across different versions of node
# For more information see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-nodejs

name: Node.js CI

on:
push:
branches: [ "main" ]
pull_request:
branches: [ "main" ]

jobs:
build:

runs-on: ubuntu-latest

strategy:
matrix:
node-version: [18.x]
# See supported Node.js release schedule at https://nodejs.org/en/about/releases/

steps:
- uses: actions/checkout@v4
- name: Use Node.js ${{ matrix.node-version }}
uses: actions/setup-node@v3
with:
node-version: ${{ matrix.node-version }}
cache: 'npm'
- run: npm ci
- run: npm run build --if-present
- run: npm test
11 changes: 5 additions & 6 deletions docs/rules/always-camel-case.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,28 +4,27 @@

## Rule Details

This rule aims to...
This rule aims to enforce camal case in naming things.

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

```js
// fill me in
let a_b = 1;
```

Examples of **correct** code for this rule:

```js
// fill me in
let aB = 1;
```

### Options

If there are any options, describe them here. Otherwise, delete this section.


## When Not To Use It

Give a short description of when it would be appropriate to turn off this rule.


## Further Reading

If there are other links that describe the issue this rule addresses, please include them here in a bulleted list.

0 comments on commit 05a8181

Please sign in to comment.