Thanks for the PR, @fregante!

typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community.

The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately.

Thanks again!

🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. As a thank you, your profile/company logo will be added to our main README which receives thousands of unique visitors per day.

Nx Cloud Report

CI ran the following commands for commit ef691f0. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

Status	Command
	nx run-many --target=typecheck --all --parallel
	nx test @typescript-eslint/eslint-plugin-internal
	nx test @typescript-eslint/eslint-plugin-tslint
	nx test @typescript-eslint/eslint-plugin
	nx test @typescript-eslint/parser
	nx test @typescript-eslint/experimental-utils
	nx test @typescript-eslint/scope-manager
	nx test @typescript-eslint/visitor-keys
	nx test @typescript-eslint/typescript-estree
	nx run-many --target=build --all --parallel
	nx test @typescript-eslint/eslint-plugin-tslint
	nx test @typescript-eslint/eslint-plugin
	nx test @typescript-eslint/parser
	nx test @typescript-eslint/experimental-utils
	nx test @typescript-eslint/scope-manager
	nx test @typescript-eslint/visitor-keys
	nx prebuild @typescript-eslint/types
	nx test @typescript-eslint/typescript-estree
	nx run-many --target=build --all --parallel

Sent with 💌 from NxCloud.

This is genius!
I've been meaning to investigate the "issue form" config - so it's great to have an example to work from. We need to change all our templates to these!

I need to have a bit of a think about if we want any additional fields in the template.
I'll get back to this shortly.

I've been using forms for a month in a repo and generally I think too many fields are counterproductive, especially if their content is generally mixed together. In some cases I'm thinking about adding a generic "describe your issue" field and then add required checkboxes like:

• I included the steps to reproduce
• I included screenshots of the issue, if visual
• I included console logs, if any

But yeah this varies by repo and requirements