Skip to content
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

feat(Next > TypeScript): Add TypeScript with strict enabled #576

Merged
merged 45 commits into from
Aug 30, 2023
Merged

Conversation

danactive
Copy link
Owner

@danactive danactive commented Feb 18, 2023

Summary

TypeScript is enabled with Next.js though not all files are converts some stay as JSX which is okay for this PR as there are issues to resolve before merging.

There are two major errors based on my JavaScript migration to TypeScript:

  1. The GeneralList and List are passing a React component around, but I don't know how to set the type properly - Replaced with MUI and deleted components
  2. SlippyMap has some GeoJSON types mismatch

Test plan

Run tsc currently reports "Found 4 errors in 3 files."
Run npm run lint and some of the TypeScript types are breaking JS Lint rules
Run npm run test and GenericList/tests/index.test.jsx has one test breaking
Rum npm run build which currently fails due to lint errors

@vercel
Copy link

vercel bot commented Feb 18, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
history ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 30, 2023 7:58pm

# Conflicts:
#	next/package-lock.json
#	next/package.json
@danactive danactive changed the title feat(Next > TypeScript): Add TypeScript with some errors, lint, test feat(Next > TypeScript): Add TypeScript with strict enabled Aug 30, 2023
@danactive danactive merged commit d8f4599 into main Aug 30, 2023
5 checks passed
@danactive danactive deleted the typescript branch August 30, 2023 20:03
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.

1 participant