Skip to content

Conversation

@andrea78
Copy link

@andrea78 andrea78 commented Apr 4, 2025

This pull request addresses issue #321, where certain SVG path data was not being parsed correctly, leading to rendering issues in the whiteboard application. The root cause was identified in the outdated path-data-polyfill.js file. This PR replaces it with an updated version from jarek-foksa/path-data-polyfill commit 115f8ab, which includes improved path parsing logic and bug fixes.

By opening a pull request, I certify that I hold the intellectual property of the code I am submitting, and I am granting the initial authors of WBO a perpetual, worldwide, non-exclusive, royalty-free, and irrevocable license to this code.

andrea78 added 2 commits April 4, 2025 02:54
This pull request addresses issue #321, where certain SVG path data was not being parsed correctly, leading to rendering issues in the whiteboard application. The root cause was identified in the outdated path-data-polyfill.js file. This PR replaces it with an updated version from jarek-foksa/path-data-polyfill commit 115f8ab, which includes improved path parsing logic and bug fixes.
@lovasoa lovasoa requested a review from Copilot April 4, 2025 13:11
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.

Copy link
Owner

@lovasoa lovasoa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi ! Did you test your changes ? They do not seem to fix the issue, for me.

@andrea78
Copy link
Author

andrea78 commented Apr 5, 2025

Hi! Thanks for your feedback.
I noticed that the code from my pull request appears to be identical to the one committed in a6aa0c3. Could you clarify what exactly didn’t work? Just trying to understand, since it looks like the same changes were already applied.

I’m a bit confused, since the exact same code was committed shortly after my PR was submitted and marked as 'not working'. Could you clarify why the commit was accepted, but the PR was not?

Thanks!

@lovasoa
Copy link
Owner

lovasoa commented Apr 5, 2025

No, the upstream was updated with the required fix after you pulled it.

@andrea78 andrea78 closed this Apr 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants