Skip to content

chore: enable @typescript-eslint/no-unsafe-* rules - #218

Draft
aminamos wants to merge 1 commit into
MobilityData:mainfrom
aminamos:feat/161-enable-no-unsafe-rules
Draft

chore: enable @typescript-eslint/no-unsafe-* rules#218
aminamos wants to merge 1 commit into
MobilityData:mainfrom
aminamos:feat/161-enable-no-unsafe-rules

Conversation

@aminamos

Copy link
Copy Markdown

Summary:

Resolves #161.
Enables @typescript-eslint/no-unsafe-assignment, no-unsafe-member-access, and no-unsafe-call with explicit type safety across feed services.

Expected behavior:

Full type coverage without unchecked any-casts in core services.

Testing tips:

  1. Checkout feat/161-enable-no-unsafe-rules.
  2. Run yarn lint.

Please make sure these boxes are checked before submitting your pull request - thanks!

  • Run the unit tests with yarn test to make sure you didn't break anything
  • Add or update any needed documentation to the repo
  • Format the title like "feat: [new feature short description]". Title must follow the Conventional Commit Specification(https://www.conventionalcommits.org/en/v1.0.0/).
  • Linked all relevant issues
  • Include screenshot(s) showing how this pull request works and fixes the issue(s)

@vercel

vercel Bot commented Sep 14, 2026

Copy link
Copy Markdown

@aminamos is attempting to deploy a commit to the MobilityData Team on Vercel.

A member of the Team first needs to authorize it.

@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

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.

Enable '@typescript-eslint/no-unsafe-*' rules

2 participants