rowrowrowrow

@long2ice Also looking forward to a new release! Thanks!

@rt2zz Hoping you can take a look at this and see if it makes sense, thanks!!

Hi @JacobJaffe , does this break the pause() -> persist() usecase for you? I think to answer your question, for me and without the proposed change, the rehydrate dispatch is...

I just tried it out, for me this doesn't resolve the use case. Once it returns in that example it doesn't attempt to get data to rehydrate and after setting...

Ya, for me the proposed changes seem necessary and it works great/as expected now, but then again it might break for cases other than mine. I just haven't experienced any...

@JacobJaffe I just pushed the changes with your recommendations. It's working great for me can you let me know if you find any issues or if we need to approach...

Sorry for the convoluted explanation. I'll work on an example if this psuedo-code doesn't help. 1. const sourceFilePond = React.createElement(FilePond,{files : mockFiles}); 2. const processedMockFiles = sourceFilePondFiles; // Gathered from...

Thanks for taking the time, I realized that this is the same issue as adding initial files using the addFiles method even though the files are passed as props. So...

@rikschennink Ya I'm currently filtering mock vs. real using metadata because it's a simpler approach. But, the processed mock file should have all the data to recreate itself internally or...

bump, I'm not sure if the PR for this works entirely but this functionality is necessary and expected out of the box