fix: preserve workspace label when creating DAGs#2096
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
📝 WalkthroughWalkthroughThis PR adds workspace-aware default DAG spec logic to the DAG creation flow, improves accessibility by adding screen-reader descriptions to multiple dialog components, and restructures the DAGNameInputModal layout to move the pattern hint outside the description block. A new test suite validates the workspace-aware DAG creation behavior. ChangesWorkspace-aware DAG Creation
Dialog Accessibility & UI Improvements
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
Root cause
The header create path posted only the DAG name, unlike the empty-state create path that initialized the spec with the selected workspace label. New DAGs created from the header were therefore treated as default-workspace DAGs and failed the selected-workspace check.
Tests
pnpm vitest run src/features/dags/components/common/__tests__/CreateDAGButton.test.tsxpnpm vitest run src/features/dags/components/dag-execution/__tests__/StartDAGModal.test.tsxpnpm vitest run src/pages/agent-settings/__tests__/ModelFormModal.test.tsxpnpm typecheckpnpm testpnpm buildSummary by CodeRabbit
Release Notes