Syncable - SyncedResourceSaved event is triggered even if there are no changes compared synced attributes about tenancy

[stancl]

We have a fix for this in v4 now. Might backport the fix to v3, though we don't want to make many changes to resource syncing in v3. v4 has a major rewrite of the logic since there are some bugs in v3 that are hard to fix in a backwards-compatible way.

[stancl]

I'll close this now since as mentioned, we don't really want to change how resource syncing works in v3. With this issue being fixed in v4, and v4 having a general resource syncing rewrite to address some of the other bugs discovered in v3 resource syncing.

[stancl]

Could you expand on this issue a bit? We're aware of some bugs in resource syncing and are addressing them in v4 now.

[illambo]

Yes. IMO at the moment I see one main issues: performance (consumption of resources / execution time, any jobs to be queued, ..). Perhaps a "sync updates" event (only triggered in case of modification of the synced attributes) to listen for might be more profitable.
What do you think?

[emre-ayhan]

I have the same isso even when navigating between pages triggers the sync evet. Using with laravel 10 inertia