Skip to content
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

i17: Stabilize Onsave #21

Merged
merged 3 commits into from
Oct 24, 2022
Merged

i17: Stabilize Onsave #21

merged 3 commits into from
Oct 24, 2022

Conversation

jollyjerr
Copy link
Owner

This PR gives onSave a stable definition even if the client needs to update the definition frequently. This makes it where onSave will not be called just because the function definition changed.

closes #17

@jollyjerr jollyjerr merged commit 4cfc8a2 into main Oct 24, 2022
@jollyjerr jollyjerr deleted the i17/stable-onsave branch October 24, 2022 03:33
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.

onSave is called if onSave changes. Can this be optional?
1 participant