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

Add isOnUnmount to onSave callback #31

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

jlopezxs
Copy link

Hello there!

I'm currently using this library for autosave, and I must say I appreciate its simplicity. However, I've encountered a specific use case that the library doesn't quite address. I perform a request in each onSave, but I'd prefer not to invalidate my cache in every request, I prefer to do only when the component unmount. As of now, I can achieve this by creating a separate useEffect just for that purpose or implementing it the existing onSave callback.

I'm curious to know if you've considered implementing a feature in the library. It would be great if the library could provide an option to know if is an onmount callback or not.

What are your thoughts on this idea?

Copy link
Owner

@jollyjerr jollyjerr left a comment

Choose a reason for hiding this comment

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

One bit of feedback but this looks good to me 👍🏼 I'm wondering how difficult it would be to add a test for this? No worries if it turns out to be a lot of trouble

@@ -4,7 +4,7 @@ export interface CommonProps<TData, TReturn> {
/** The controlled form value to be auto saved */
data: TData;
/** Callback function to save your data */
onSave: (data: TData) => Promise<TReturn> | TReturn | void;
onSave: (data: TData, isOnUnmount: boolean) => Promise<TReturn> | TReturn | void;
Copy link
Owner

Choose a reason for hiding this comment

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

Suggested change
onSave: (data: TData, isOnUnmount: boolean) => Promise<TReturn> | TReturn | void;
onSave: (data: TData, meta: {unmounting: boolean}) => Promise<TReturn> | TReturn | void;

Could we wrap this in an object so if we ever need to add more metadata it is not a breaking change to the callback's contract?

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.

None yet

2 participants