DataGrid InLine Editing Non-null check

Hello, excuse me, I have a problem:
I follow this article: DataGrid InLine Editing, to implement a similar method, now encountered a problem, when click a line of data to edit, then the data in a cell will be emptied, and directly click the Add button to add new data, which will trigger verification, the prompt cannot be empty, the sample in the website this prompt will only flash, and the empty content will be saved. The idea of my project is not to save the empty data but to restore the original data, but the problem is that my empty hint will always exist. Is there any way to fix it? I don't know what the problem is.

Here are the steps and the last one is the ever-present hint
1、


2、

3、


4、

This is the video I recorded:
que.zip (2.0 MB)

Our online demo does not seem to show such behavior. You cannot add an empty item. Make sure you handle the RowCreate event of the grid.

Thank you for your reply, maybe there is a problem with my description. It is not that I cannot add empty items, but when editing a data as empty, click the Add button, and the pop-up prompt of non-empty verification will always exist.

I still don't understand what the problem is. Try to reproduce it by editing some of our online demos so we can test it ourselves.

It can be said that the non-empty judgment of the cell in the edit state is the event that loses focus, that is, when I set the data of a cell to empty, when I click the Add row button, it will trigger this non-empty judgment, is there any way to not perform the non-empty judgment when I click the Add button?
My current thinking is: when editing a line of content, if you do not click save and click the Add line button, the previously edited line will be restored to the original data, and the online sample is to save the unedited data.

No, the Add button always triggers validation.

Ok, let me look at it again and see if the online sample can be reproduced

This may have something to do with the nuget package version I'm referencing, and I'm still using version 4.15 instead of the latest one