Skip to content

Conversation

TecReaGroup
Copy link
Contributor

Description

Update _erasePoint, and check if the erasing effect is effective, avoid affecting the undo stack.

Checklist

  • My PR title is in the style of conventional commits
  • All public facing APIs are documented with dartdoc
  • I have added tests to cover my changes

@TecReaGroup TecReaGroup force-pushed the main branch 2 times, most recently from 495ef23 to cdd685a Compare May 24, 2025 06:58
Copy link
Owner

@timcreatedit timcreatedit left a comment

Choose a reason for hiding this comment

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

Thank you so much for your contribution! I have a couple tiny comments, otherwise this looks good :)

@TecReaGroup TecReaGroup requested a review from timcreatedit June 4, 2025 07:12
@timcreatedit
Copy link
Owner

Hi @TecReaGroup, you re-requested a review but it seems like you didn't change anything. Did you see my comments?

@TecReaGroup TecReaGroup force-pushed the main branch 2 times, most recently from 441d9c6 to 10aba12 Compare June 4, 2025 08:20
@TecReaGroup
Copy link
Contributor Author

OK, I have modified it according to your request, please review it.

Note: Thank you for your tolerance. This is the first time to submit a PR formally. There are many mistakes. I am so sorry.

@timcreatedit timcreatedit changed the title fix: eraser logic, if the eraser actually erased something, update the value, avoid null eraser affecting the undo stack fix: eraser doesn't affect undo history if it didn't actually erase anything Jun 6, 2025
@timcreatedit timcreatedit merged commit 9900a8d into timcreatedit:main Jun 6, 2025
1 of 2 checks passed
@timcreatedit
Copy link
Owner

Thank you so much for your contribution @TecReaGroup !

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