feat: add default_action field to files-actions-menu registration

[jvdp]

fixes #748

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

📝 Walkthrough

Walkthrough

This PR adds a defaultAction field to file action menu registration. The OCS V2 controller accepts and validates the parameter ('' → null, or 'default'/'hidden'), the service persists it, the entity exposes and serializes default_action, a migration adds the nullable DB column, and the frontend maps fileAction.default_action to action.default. PHP and JS tests cover valid, empty, and invalid inputs.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 33.33% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'feat: add default_action field to files-actions-menu registration' clearly and concisely describes the main change in the changeset.
Description check	✅ Passed	The description 'fixes #748' is related to the changeset, linking to the issue requesting default file action registration support.
Linked Issues check	✅ Passed	The PR implements the proposed solution from issue #748 by adding a default_action field to the files-actions-menu registration API with proper validation and persistence across PHP and JavaScript layers.
Out of Scope Changes check	✅ Passed	All changes are directly related to implementing default_action support: controller endpoint updates, database entity and migration, service layer updates, JavaScript frontend changes, and corresponding tests.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[oleksandr-nc]

@jvdp , could you rebase the PR when you have time?

[jvdp]

@oleksandr-nc rebase done and also fixed up a bit. The second commit is to fix a bug found on CI.

[oleksandr-nc]

@jvdp the PR looks really good! ☀️

Could you squash all commits into one? After that we can merge this

[oleksandr-nc]

@jvdp , thank you for taking effort and working on this - good job.

[jvdp]

@oleksandr-nc you're welcome and thanks for merging!

[github-actions]

Hello there,
Thank you so much for taking the time and effort to create a pull request to our Nextcloud project.

We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process.

Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6

Thank you for contributing to Nextcloud and we hope to hear from you soon!

(If you believe you should not receive this message, you can add yourself to the blocklist.)