Conversation
|
|
|
Important Review skippedToo many files! This PR contains 232 files, which is 82 over the limit of 150. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (13)
📒 Files selected for processing (232)
You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 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 |
|
Nice feature enhancement, but I think this PR is too large, making it difficult to review |
Add connector routing/jumps, expanded shape libraries, grid and snap controls, properties panel improvements, and export/import coverage for edgeless workflows, with new integration and e2e tests.
758f76d to
794dfad
Compare
|
Thank you @darkskygit for taking the time to review and consider this PR. I see that I must have n00bed the merge with canary as all merge edits were included in this PR. I am happy to break into smaller PR's - it's some work and happy to do it if y'all are serious about considering this for inclusion. I propose the following PR:
Keen to hear your thoughts. |
I think enhancing the connector is a great start. |
Diagramming power-up - Drawio like diagramming native to AFFiNE
I built this to make AFFiNE edgeless viable for my day-to-day diagramming workflow (draw.io-like use cases) without switching tools for text, structure, and export/import.
I know this is a large change set and that reviewing it will require real effort. I want to explicitly acknowledge that up front.
Please see #14471 for a detailed view.
What this PR adds
Validation status
I’ve run extensive test work across unit/integration/e2e while building this and tracked feature coverage + known failures in the related GitHub discussion thread (including rerun notes and failing cases).
There are still failures in the broader suite; some appear to reproduce on upstream/canary as baseline instability, not only from this branch.
Maintainer expectations
I understand this is not a “quick review” PR.
If you’re open to it, I can do whatever reduces your review burden:
I’m committed to working through review feedback with you, including iterative follow-up PRs until this is in a shape you’re comfortable with.
Vibe AF
Almost entirely vibe coded with Claude and Codex
Enjoy
🤗