fix(linter): do not generate docs.recommended property #28009
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
☁️ Nx Cloud ReportCI is running/has finished running commands for commit f99c799. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 4 targets
Sent with 💌 from NxCloud. |
| @@ -84,7 +84,6 @@ export const rule = ESLintUtils.RuleCreator(() => __filename)({ | |||
| type: 'problem', | |||
| docs: { | |||
| description: \`\`, | |||
| recommended: 'error', | |||
There was a problem hiding this comment.
This was an old migration, I don't think it technically matters if it's updated or not?
There was a problem hiding this comment.
It didn't ever serve any purpose so it's just setting people up for an issue down the road if they run the migration right now
(cherry picked from commit 00b3dd2)
|
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Current Behavior
We still generate
docs.recommendedwhich is not on the types.Expected Behavior
We do not generate
docs.recommended.Related Issue(s)
Fixes #