-
-
Notifications
You must be signed in to change notification settings - Fork 206
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inconsistent onchange results #536
Comments
if i understand correctly, you want to enable a save button if the sheet is dirty as compared to the last state? |
yes |
id suggest using the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have a conditional save button for fortunesheet which checks if the previous state and updates state is same then it will be enabled for user to save. In followig scenario we are getting inconsistent results in onchange:
1)When we copy paste something it gives some additional keys named - luckysheet_alternateformat_save:[] , luckysheet_conditionformat_save:[], luckysheet_select_save.
2)We save the state in db.
3)When user comes back to the page onChange runs while rendering the page and checks if previous state(saved in db) and current state is same at this time we dont get the additional keys we got at 1st point which makes the save button enabled all the time if we have saved any report after copy paste.
Data we are getting for the same sheet should be consistent is there any workaround for this.
Also does those keys have signifance in rendering the fortunesheet if not can we ignore those while saving data in db so that this conflict wont occur.
The text was updated successfully, but these errors were encountered: