nocobase-bugfix
NocoBase Bugfix
Defaults
- Fix v2 only. Treat v1 schema code as reference unless the user asks to modify v1.
- Prefer code-path analysis, tests, and local reproduction before browser use. Open a browser only when explicitly requested or necessary.
- Make the smallest safe change that fixes the cause, not just the symptom.
- Search with
rgfirst.
Where To Look
packages/core/client/src/flowpackages/core/flow-engine/srcpackages/core/client-v2- Plugin packages:
packages/plugins,packages/pro-plugins/@nocobase
For plugin v2 bugs, search the plugin package first, then inspect src/client-v2 and src/client/models.
Workflow
More from jiannx/agent-skills
nocobase-v2-flow-upgrade
Upgrade existing NocoBase v1 plugins to v2 FlowModel or field-model architecture with behavior parity. Use for migration planning, implementation, parity validation, and pitfalls around request payloads, settings ownership, i18n namespaces, roles persistence, flow variables, and editor integrations.
9fe-quality-operations
Prepare frontend projects for reliable delivery with testing, performance review, observability, release strategy, and production-readiness checks.
2fe-data-mock-state
Design frontend data layers, server-state handling, adapters, mock strategies, and state ownership with stable contracts and low integration churn.
2fe-routing-permission
Design frontend navigation, route ownership, URL state, auth boundaries, and permission systems with explicit access rules and user-state handling.
2fe-design-implementation
Implement product-grade frontend UI from design artifacts with consistent interaction patterns, theme-driven styling, responsive behavior, and design verification.
2fe-product-development
Build product-grade frontend projects with implementation guidance optimized for React ecosystems. Covers bootstrap, architecture, design implementation, data flow, testing, observability, release strategy, and long-term maintainability.
2