Skip to content

enforce dangling comma / update jsdoc for getSubnameForRecipient #11266

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 12, 2025

Conversation

kesselb
Copy link
Contributor

@kesselb kesselb commented Jun 12, 2025

The ESLint comma-dangle rule issues warnings but doesn't fail the CI. Running npm run lint:fix adds missing commas automatically. This often leads to committing unrelated changes. Now, the CI enforces the dangling comma rule.

@kesselb kesselb self-assigned this Jun 12, 2025
@kesselb kesselb force-pushed the docs/missing-jsdoc-warning-forsubname branch from c4adecc to 17417fc Compare June 12, 2025 14:59
@kesselb kesselb marked this pull request as ready for review June 12, 2025 15:00
kesselb added 2 commits June 12, 2025 17:00
Signed-off-by: Daniel Kesselberg <mail@danielkesselberg.de>
The ESLint comma-dangle rule issues warnings but doesn't fail the CI. Running npm run lint:fix adds missing commas automatically. This often leads to committing unrelated changes. Now, the CI enforces the dangling comma rule.

Signed-off-by: Daniel Kesselberg <mail@danielkesselberg.de>
@kesselb kesselb force-pushed the docs/missing-jsdoc-warning-forsubname branch from 17417fc to 79970b2 Compare June 12, 2025 15:00
@ChristophWurst ChristophWurst merged commit 9f1be5c into main Jun 12, 2025
42 checks passed
@ChristophWurst ChristophWurst deleted the docs/missing-jsdoc-warning-forsubname branch June 12, 2025 19:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants