Enhancement: Make tables import asynchronous

[Koc]

Right now module not ready to import large tables. This PR improves import flow by moving it into asynchronous job.

🗒️ TODO:

• make import work for uploaded (not selected) files as well
• revert changes to old endpoints, introduce new one instead
• properly parse activity notification
• fix pipelines
• add new tests

🔍 Preview

nextcloud-tables-2025-05-26_18.14.20.mp4

[blizzz]

Please keep in mind, existing API shall remain stable, but may be flagged deprecated.

[Koc]

@blizzz What exactly do you mean? Do not change already existent endpoint (keep it synchronous) but introduce v2/v3 for async tasks (even if this endpoints will be not in use on FE side)?

[blizzz]

@blizzz What exactly do you mean? Do not change already existent endpoint (keep it synchronous) but introduce v2/v3 for async tasks (even if this endpoints will be not in use on FE side)?

Yes, exactly. The old ones can get the @deprecated annotation and point to the new method.

[blizzz]

replied to questions

[Koc]

@blizzz I've reverted all changes to old endpoints. So they are completely untouched. Now we have also scheduleImportIn(Table|View) + scheduleImportUploadIn(Table|View). FE uses new endpoints.

Also it is possible to import uploaded files (app data used under the hood)

[blizzz]

It is shaping up nicely! It looks like a file was not committed. Did not test yet.

[blizzz]

The underlying file does not seem to be committed.

[Koc]

this exception should be located somewhere in the core. I've just stolen code to publish/parse activity from another module

[blizzz]

Oh, indeed. But this is available only as of NC 30, on main we still support 29.

[Koc]

ok, how to deal with that? Can we just bump minimum NC supported version to 30? Like in other modules: Collectives, Forms, etc

[blizzz]

We weed need to branch-off, which of course is possible. We were aiming for September originally. Related changes (version bump and housekeeping) would happen in a separate PR. I'll get back about it.