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.

Sign up for GitHub

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

Jump to bottom

🚀 Feature: Blog post on why TypeScript is essential for type information #298

Closed
3 tasks done
JoshuaKGoldberg opened this issue Sep 20, 2024 · 0 comments · Fixed by #299
Closed
3 tasks done

🚀 Feature: Blog post on why TypeScript is essential for type information #298

JoshuaKGoldberg opened this issue Sep 20, 2024 · 0 comments · Fixed by #299
Assignees
@JoshuaKGoldberg
Labels
status: accepting prs Please, send a pull request to resolve this! type: feature New enhancement or request

Comments

@JoshuaKGoldberg
Copy link
Owner

JoshuaKGoldberg commented Sep 20, 2024 •
edited
Loading

Bug Report Checklist

  • I have tried restarting my IDE and the issue persists.
  • I have pulled the latest main branch of the repository.
  • I have searched for related issues and found none that matched my issue.

Overview

Splitting out of #296 / #284: one of the motivators why I'd write a linter in TypeScript is that it has much easier compatibility with native TypeScript APIs for type information.

(this actually isn't my biggest motivator - developer compatibility is - but it's important to note as a secondary point)

Additional Info

💖
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JoshuaKGoldberg JoshuaKGoldberg

Labels
status: accepting prs Please, send a pull request to resolve this! type: feature New enhancement or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: blog post: 'Why Typed Linting Needs TypeScript Today' JoshuaKGoldberg/dot-com
1 participant
@JoshuaKGoldberg