Skip to content

feat: add lint rules and an ignore option to lintInput - #160

Merged
otnc merged 1 commit into
mainfrom
feat/lint-more-rules
Oct 14, 2026
Merged

otnc merged 1 commit into
mainfrom
feat/lint-more-rules

Conversation

@otnc

@otnc otnc commented Oct 14, 2026

Copy link
Copy Markdown
Owner

Summary

  • Fix bug(s)
  • New feature(s)
  • Others

Add six lint rules to lintInput (duplicate item ids, future dates, relative URLs in content/description, enclosure type/length, overlong or HTML titles, and a paging suggestion past 100 items). Every rule, including the existing ones, now has an id (LintRuleId), and lintInput takes an optional third argument { ignore, now }. The return type is still string[], and existing messages are unchanged. README (en/ja) is updated through base/README.base.md.

Why?

The existing lint output mostly reports missing fields. The mistakes that bite in practice are duplicated ids, timezone mix-ups, relative URLs that feed readers can't resolve, and enclosures with a zero length. Rule ids let a project accept the warnings it doesn't care about instead of dropping the whole check.

Related issue(s)

closes

Check

  • Check if duplicate PR(s) already exist.
  • Read CONTRIBUTING.md (rules)
  • Run pnpm check (lint & format)
  • Run pnpm test (functions test)
  • Run pnpm build (dist/)
  • (optional) Run pnpm test:coverage and check nothing new went uncovered

New rules: duplicate ids, future dates, relative URLs in content, enclosure type/length, overlong or HTML titles, and a paging suggestion past 100 items. Every rule has an id, and lintInput accepts { ignore, now }.
@github-actions github-actions Bot added enhancement New feature or request to main for Pull Request to main labels Oct 14, 2026
@otnc
otnc merged commit 87b61b4 into main Oct 14, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request to main for Pull Request to main

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant