-
Notifications
You must be signed in to change notification settings - Fork 896
Lint Plugin #3833
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
base: main
Are you sure you want to change the base?
Lint Plugin #3833
Conversation
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
🦋 Changeset detectedLatest commit: 5aae415 The changes in this PR will be included in the next version bump. This PR includes changesets to release 61 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@claude review this |
Claude finished @zbeyens's task —— View job Code Review for Lint Plugin PRI've completed a comprehensive review of the lint plugin implementation. Overall, this is a substantial feature addition that provides valuable functionality, but there are several areas that need attention before merging. Todo List
SummaryThe lint plugin introduces a powerful text validation system with customizable rules, similar to ESLint for document content. While the functionality is impressive, there are significant issues with type safety, performance, test coverage, accessibility, and documentation that should be addressed. 🔴 Critical Issues1. Type Safety & Runtime Errors
2. Memory Leak RiskIn 3. Missing Error Handling
🟡 Performance Concerns
🟡 Test Coverage GapsWhile some areas have excellent coverage (decorateLint, caseLintPlugin), critical gaps exist:
🟡 Accessibility Issues
🟡 Documentation IssuesThe documentation in
🟢 What Works Well
📋 RecommendationsImmediate fixes needed:
Before merge:
Future improvements:
ConclusionThis is a valuable feature that will benefit users, but it needs refinement before merging. The core functionality is solid, but type safety, error handling, test coverage, and accessibility need immediate attention. I recommend addressing at least the critical issues and improving test coverage before merging. |
@claude changeset |
Claude finished @zbeyens's task —— View job Changeset CreatedSuccessfully created changeset and updated the changelog for the lint plugin PR. Todo List
Changes Made
The changeset bot should now recognize these changes and update its comment accordingly. |
- Add changeset for new @udecode/plate-lint package - Document changes to @udecode/plate-floating and @udecode/slate-utils - Update component changelog for lint-leaf and lint-popover UI components Co-authored-by: Ziad Beyens <zbeyens@users.noreply.github.com>
/changeset again, you did a mistake about splitting |
Claude finished @zbeyens's task —— View job Changeset Files CorrectedI've successfully split the changeset into separate files as required. Each package now has its own changeset file: Todo List
Changes Made
Each changeset file now contains only one package in its frontmatter, following the critical requirement for proper semantic versioning. |
Each package now has its own changeset file as required Co-authored-by: Ziad Beyens <zbeyens@users.noreply.github.com>
Checklist
yarn typecheck
yarn lint:fix
yarn test
yarn brl
yarn changeset