Skip to content

Jm/eslint formatting docs#614

Closed
JonathanMatthey wants to merge 10 commits into
mainfrom
jm/eslint-formatting-docs
Closed

Jm/eslint formatting docs#614
JonathanMatthey wants to merge 10 commits into
mainfrom
jm/eslint-formatting-docs

Conversation

@JonathanMatthey

@JonathanMatthey JonathanMatthey commented Nov 19, 2025

Copy link
Copy Markdown
Collaborator

Changes

  • added eslint
  • CI workflow
  • updated readme
  • Separated combined list items in components - many steps were incorrectly merged on single lines
  • Removed
    tags breaking up ordered lists within components
  • Fixed indentation for nested content (images, notes, cards) inside list items
  • Removed client:load from components - Astro components don't support hydration directives
  • Fixed mismatched code fence backticks causing parsing errors

@netlify

netlify Bot commented Nov 19, 2025

Copy link
Copy Markdown

Deploy Preview for webmonetization-preview ready!

Name Link
🔨 Latest commit 54c2a1c
🔍 Latest deploy log https://app.netlify.com/projects/webmonetization-preview/deploys/69205e1705401500089c3e49
😎 Deploy Preview https://deploy-preview-614--webmonetization-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@JonathanMatthey JonathanMatthey force-pushed the jm/eslint-formatting-docs branch from ade0295 to f5bf059 Compare November 19, 2025 02:35
@JonathanMatthey JonathanMatthey force-pushed the jm/eslint-formatting-docs branch from 5538b26 to 23e532a Compare November 19, 2025 02:57

@Anca2022 Anca2022 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One last thing: WM doesn't have a PR template like the rest of the repos; can you please add one in? 😇

Comment thread package.json Outdated
"preview": "astro preview",
"astro": "astro"
"astro": "astro",
"lint": "eslint .",

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

let's keep this consistent with the rest of the docs repos
format : Format code and fix linting issues
lint : Check code formatting and linting |

Comment thread README.md Outdated
| `bun run build` | Build your production site to `./dist/` |
| `bun run preview` | Preview your build locally before deploying |
| `bun run lint` | Check code for linting errors |
| `bun run lint:fix` | Automatically fix linting errors where possible |

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here - format and lint for consistency

Comment thread .github/workflows/lint-and-format.yml Outdated
run: bun install

- name: Check code quality
run: bun run check

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After making the changes in package.json, this command should become bun run lint

Comment thread package.json
"starlight-links-validator": "^0.17.0",
"typescript": "^5.8.3"
},
"devDependencies": {

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This repo doesn't have Biome, like the rest of docs repos, and doesn't format .astro files

Comment thread CONTRIBUTING.md

```sh
bun run lint:fix
```

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here - format and lint for consistency

Comment thread README.md Outdated

You can substitute the bun commands with your chosen package manager's commands.

Before submitting a PR, make sure your code passes linting by running `bun run lint`. If there are any issues that can be automatically fixed, use `bun run lint:fix`.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Before submitting a PR, make sure your code passes linting by running `bun run lint`. If there are any issues that can be automatically fixed, use `bun run lint:fix`.
Before submitting a PR, make sure your code passes linting by running `bun run lint`. If there are any issues that can be automatically fixed, use `bun run format`.

@Anca2022

Copy link
Copy Markdown
Collaborator

Final-final: please mention Biome in the README file, alongside eslint and prettier

@JonathanMatthey JonathanMatthey deleted the jm/eslint-formatting-docs branch November 28, 2025 20:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants