The xyflow/xyflow project, an open-source library for building node-based UIs with React and Svelte, has seen limited progress over the past 30 days, with persistent issues related to edge interactions and UI inconsistencies remaining unresolved.
Recent issues and pull requests (PRs) indicate ongoing struggles with edge behavior and node interactions. Notable issues include #4659 concerning connection handles, and #4658 regarding lasso selections, both highlighting user challenges with the library's current functionality. The development team has been actively addressing these concerns through PRs like #4653, which aims to fix viewport dimension calculations.
Recent activities show a focus on bug fixes and release preparations, with Peter Kogo and Moritz Klack leading efforts in testing and documentation updates. However, some team members like James Kairu and Alexander Horner have not contributed recently.
| Timespan | Opened | Closed | Comments | Labeled | Milestones |
|---|---|---|---|---|---|
| 7 Days | 10 | 8 | 13 | 5 | 1 |
| 30 Days | 37 | 44 | 82 | 15 | 1 |
| 90 Days | 121 | 115 | 350 | 62 | 1 |
| 1 Year | 267 | 200 | 801 | 121 | 2 |
| All Time | 1944 | 1860 | - | - | - |
Like all software activity quantification, these numbers are imperfect but sometimes useful. Comments, Labels, and Milestones refer to those issues opened in the timespan in question.
| Developer | Avatar | Branches | PRs | Commits | Files | Changes |
|---|---|---|---|---|---|---|
| Moritz Klack |  |
1 | 5/5/0 | 31 | 31 | 894 |
| Peter Kogo |  |
1 | 5/6/0 | 26 | 35 | 584 |
| github-actions[bot] |  |
1 | 4/4/0 | 4 | 18 | 217 |
| Braks |  |
1 | 3/2/0 | 4 | 6 | 87 |
| None (jameskairu) | 0 | 1/0/0 | 0 | 0 | 0 | |
| Alexander Horner (alexanderhorner) | 0 | 1/0/1 | 0 | 0 | 0 |
PRs: created by that dev and opened/merged/closed-unmerged during the period
The xyflow/xyflow GitHub repository currently has 84 open issues, with recent activity indicating a mix of bug reports and feature requests. Notably, several issues highlight problems with edge connections, node interactions, and UI inconsistencies across different platforms. A recurring theme is the challenges developers face when upgrading to newer versions, particularly concerning node and edge behavior.
Several issues exhibit significant user frustration, particularly around the handling of custom nodes and edges. For instance, issues like #4605 and #4318 indicate that users are encountering unexpected behaviors when dragging nodes or connecting edges. There is also a notable number of requests for improved documentation and examples to facilitate smoother transitions between versions.
Issue #4659: Rotation function, custom connection handle, the connection line is too far away from the handle
Issue #4658: Edges with selectable set to false are still included in lasso selections
Issue #4652: Calculate viewport dimensions in fitView action
Issue #4650: isVisible support for Handle
Issue #4647: React flow edges are not getting mounted on UI if browser zoom level is reduced to 80%, 90% or increased to 110%
Issue #4604: Version 11.11.3: onNodeClick Not Working with Touchpad Clicks
Issue #4602: The “Handle” only indicates the type, but is used here as a value.
Issue #4508: SvelteFlow: Attach an edge to an edge.
The analysis highlights key areas where user experience can be improved through better documentation and addressing specific bugs related to node and edge interactions. The project appears to be actively maintained, with ongoing discussions about various issues that reflect community engagement and responsiveness from the maintainers.
This overview provides insight into the current state of the xyflow project on GitHub while identifying themes that could inform future development priorities.
The xyflow/xyflow repository currently has 8 open pull requests, reflecting ongoing development and feature enhancements. The recent activity indicates a focus on bug fixes, feature additions, and improvements to existing functionalities across both React and Svelte frameworks.
PR #4660: twitter @richblood1942fl organic account
Summary
Quantified Reports
Detailed ReportsSECURITY.md file for security guidelines. Notably lacks changesets, indicating it may not trigger a version bump.PR #4653: fix(react): calculate viewport dimensions inside of fitView action
PR #4540: feat: add XYError
PR #4463: feat(hooks): useEdgesData
PR #4456: feat(types): accepts readonly arrays in props
PR #4423: Option to intersection on certain input percentage.
PR #4194: Svelte 5
PR #3169: feat(pointer-events-support): Add support for pointer events
The current state of open pull requests in the xyflow/xyflow repository reveals several themes and areas of focus:
Bug Fixes and Enhancements: The majority of recent PRs (e.g., #4653, #4540) are centered around fixing bugs and enhancing existing features, particularly related to viewport calculations and error handling mechanisms. This reflects a commitment to maintaining the stability of the library while introducing new functionalities.
Feature Additions: Several PRs introduce new features (e.g., #4463, #4423) that expand the capabilities of the library, such as improved data handling with edges and customizable intersection options. This trend indicates an active effort to cater to user demands and enhance usability.
Type Safety Improvements: The introduction of readonly arrays in props (#4456) signifies an emphasis on type safety and performance optimization within the codebase. This is crucial for maintaining robust applications built on top of the library.
Long-standing Issues: PRs like #3169 highlight ongoing discussions regarding mobile support through pointer events, which have yet to be resolved after considerable time. This could indicate either complexity in implementation or prioritization issues within the development team.
A notable concern across many open PRs is the absence of changesets (#4463, #4456). This could lead to confusion regarding versioning and release management since these changes might not trigger necessary updates in package versions upon merging.
The presence of draft PRs like #4194 suggests that while there is active development, some initiatives may be stalled due to their complexity or dependencies on other features being completed first. The long duration since creation without merging or significant updates could lead to outdated implementations if not addressed promptly.
The discussions surrounding various PRs indicate a healthy level of community engagement among contributors (e.g., feedback on PR #4578). However, it also highlights potential bottlenecks in decision-making processes that could delay important updates or features from being integrated into the main branch.
Overall, the current landscape of open pull requests in the xyflow/xyflow repository reflects a dynamic development environment focused on continuous improvement and feature enhancement while grappling with issues related to versioning management and long-standing unresolved discussions. Addressing these challenges will be crucial for maintaining momentum and ensuring that user needs are met effectively.
Peter Kogo (peterkogo)
Moritz Klack (moklick)
adoptUserNodes.GitHub Actions Bot (github-actions[bot])
Braks (bcakmakoglu)
James Kairu (jameskairu)
Alexander Horner (alexanderhorner)
The xyflow development team is actively engaged in enhancing the project through collaborative efforts, systematic testing, and continuous integration practices. The recent activities demonstrate a commitment to quality and user satisfaction in their dual-framework offerings.