-
Notifications
You must be signed in to change notification settings - Fork 536
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
Update docs to match new major release breaking changes #1655
Conversation
|
I noticed this for |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes! Love to see it
@siddharthkp Not sure if other props should be migrated, and/or if there's a linter rule to warn about this breaking change for the next major |
@SferaDev eslint-plugin-primer-react has a new release to go with the major version: https://github.com/primer/eslint-plugin-primer-react/releases |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you ✨
The linter is not catching these, ie: the |
Signed-off-by: Alexis Rico <sferadev@gmail.com>
Created primer/eslint-plugin-primer-react#21 to allow the rule to be executed on the code snippets from cc: @jfuchs |
Signed-off-by: Alexis Rico <sferadev@gmail.com>
Signed-off-by: Alexis Rico <sferadev@gmail.com>
Signed-off-by: Alexis Rico <sferadev@gmail.com>
@SferaDev - could we get the conflicts resolved so we can merge this? |
Sure thing, will update tomorrow |
Signed-off-by: Alexis Rico <sferadev@gmail.com>
Signed-off-by: Alexis Rico <sferadev@gmail.com>
Done! @mperrotti, however keep in mind that it requires primer/eslint-plugin-primer-react#21 Actually this PR is nothing else than running PS: I've reverted the changes for the files on the |
Signed-off-by: Alexis Rico <sferadev@gmail.com>
Signed-off-by: Alexis Rico <sferadev@gmail.com>
Signed-off-by: Alexis Rico <sferadev@gmail.com>
Hi! This pull request has been marked as stale because it has been open with no activity for 60 days. You can comment on the pull request or remove the stale label to keep it open. If you do nothing, this pull request will be closed in 7 days. |
Requires:
Changes:
Screenshots
Please provide before/after screenshots for any visual changes
Merge checklist
Take a look at the What we look for in reviews section of the contributing guidelines for more information on how we review PRs.