Expose `isSavingEntityRecord` and `isDeletingEntityRecord` when using `useEntityRecord`

[rmorse]

What problem does this address?

Currently useEntityRecord exposes almost all of the actions / info you might need relating to the entity record, such as record, save, edit, isResolving, hasResolved etc, but to find out if a save is in progress (to show loaders for example), we have to make a seperate select call with the same paramaters to find out if its saving.

The navigation menu is doing it here:

const { record: navigationMenu, isResolving } = useEntityRecord(
		'postType',
		postType,
		postId
);


const { isSaving, isDeleting } = useSelect(
		( select ) => {
				const { isSavingEntityRecord, isDeletingEntityRecord } =
						select( coreStore );


				return {
						isSaving: isSavingEntityRecord( 'postType', postType, postId ),
						isDeleting: isDeletingEntityRecord(
								'postType',
								postType,
								postId
						),
				};
		},
		[ postId ]
);

What is your proposed solution?

It would be nice if useEntityRecord also exposed isSavingEntityRecord and isDeletingEntityRecord as something like isSaving and isDeleting.

Assuming useEntityRecord is supposed to be an easy way to access actions and data about an entity record, then it seems these are the last two pieces of information missing.

[gziolo]

The save method returns a Promise that should play a similar role as the proposed isSaving. What would be the example when using the Promise isn’t sufficient? I’m trying to better understand current limitations.

The example linked in the description isn't the most representative as it doesn't use save from the entity but some other way to trigger persisting changes on the server.

[rmorse]

I think Adams comment summarises quite well - if we are already storing the meta data in the store (isSaving, isDeleting etc) in the store then it would be nice to expose that via the API (a convenience wrapper as Adam put it) - we might actuallly need/want this info in other components other than where the exact save was carried out and it would save us having to find a way to pass this info around.