Is there a way to execute() only after save() resolves?

This feels like a common use case so I’m wondering if this is already possible within this library.

I’d like it so that the underlying model is not changed until the Promise returned from save() resolves. Currently, the data will propagate right away throughout the template as soon as save() is executed even though the Promise is still in progress. This is a nitpick with user experience. For example, a modal is open and it’s waiting to be closed as soon as the Promise resolves but the data has already propagated to the model which creates a disconnect in the UX.

Any suggestions or workarounds?

[snewcomer]

@axsuul You are right. This is a tough issue. I forgot we need to apply the underlying changes before saving the underlying content.

Note we do have

• snapshot - https://github.com/validated-changeset/validated-changeset/blob/e6823b089cf1edaf47fa2297aa9e372b225cbb70/src/index.ts#L553

That might be of use to you. Although I’m not exactly sure how.

Cloning on our end would be tough because of the various end user shapes of objects.

I guess what I would suggest is you clone your model, pass the clone to Changeset and when the save promise is done, set the old model to the new model.

If you happen to come up with a solution we can integrate into the library, I’m all ears!!

[snewcomer]

Given the request layer for any given object can be just a plain function that accepts a hash of data; or an ember-data model that relies on associated internal state of the model to make the request, it seems the only way to make this reliably work is to allow you to extend the Changeset and implement your own save function. I’d be open to an inherent solution to this library…

https://github.com/poteto/ember-changeset#extending-the-base-ember-changeset-class