Hello,

Thanks for the work though I’m gonna close this one.
It’s mainly adding documentation to deprecated or internal methods.
The rewording of the explanations is not obviously better for me, you also switched "must inherit" into "typically extend" which is a big change mixed into the rest.

Also this reads like LLM-assisted, in which case you need to check the box and say so, see https://github.com/nextcloud/server/blob/master/.github/CONTRIBUTING.md#ai-assisted-contributions

Thanks for the work though I’m gonna close this one.

Hi @come-nc, thanks for the review and for taking a look.

I understand the concern about working on deprecated or internal APIs. My thinking here was mainly that OCP\AppFramework\App is still a very visible entry point for app developers, and some of its current docblocks seem outdated or confusing enough to be worth cleaning up even if parts of the surrounding API are older.

In particular, I wanted to remove the long dispatch() example, since it no longer feels like a great fit there, appears outdated, and would be better covered in the Developer Manual instead, as you also noted in #60780.

For the deprecated pieces, only part of the PR touches deprecated methods, so my intent was just to make the existing docs clearer while those methods remain in the codebase, especially since they were only deprecated in v34.

The current OCP class docblock also says “Any application must inherit this call”, which seems both grammatically unclear and outdated.

On changing "must inherit" to "typically extend", my intent was to make the terminology more precise. "Extend" matches the wording used in the Developer Manual, and since this is standard class inheritance rather than interface implementation, it seemed like the more accurate term. That said, "must extend" would likely be clearer, and I’d be happy to adjust that.

As a secondary point, I also thought some of the OC\AppFramework\App wording could be cleaned up for accuracy, but I understand that part may be less compelling given that it’s internal. That class docblock currently says: "Entry point for every request in your app. You can consider this as your public static void main() method." This seems potentially confusing, since it's an internal class, and the second sentence no longer seems accurate.

I’ll reply separately on the AI checkbox point as well, since it's a separate meta-issue.