feat: add classmap-authoritative to appstore-build-publish

[skjnldsv]

nextcloud/spreed#9629 (comment)
https://getcomposer.org/doc/articles/autoloader-optimization.md

Optimization Level 2/A: Authoritative class maps

How to run it?

There are a few options to enable this:

• Set "classmap-authoritative": true inside the config key of composer.json
• Call install or update with -a / --classmap-authoritative
• Call dump-autoload with -a / --classmap-authoritative

What does it do?

Enabling this automatically enables Level 1 class map optimizations.

This option says that if something is not found in the classmap, then it does not exist and the autoloader should not attempt to look on the filesystem according to PSR-4 rules.

Trade-offs

This option makes the autoloader always return very quickly. On the flipside it also means that in case a class is generated at runtime for some reason, it will not be allowed to be autoloaded. If your project or any of your dependencies does that then you might experience "class not found" issues in production. Enable this with care.

Note: This cannot be combined with Level 2/B optimizations. You have to choose one as they address the same issue in different ways.

[skjnldsv]

• Set "classmap-authoritative": true inside the config key of composer.json

Seeing this, we can also go for that option and let devs handle this on a case-by-case basis

[ChristophWurst]

Authoritative autoloaders lead to nextcloud/calendar#5191 for app store apps

[skjnldsv]

Authoritative autoloaders lead to nextcloud/calendar#5191 for app store apps

Talk is using those 🤷
I'm just following the track from nextcloud/spreed#9629 (comment)

I have zero knowledge on this :/

[nickvergessen]

I have zero knowledge on this :/

Same here, just approved the PR coming from christoph back then :P

[skjnldsv]

You're our lord and saviour @ChristophWurst 😁
What do we do then 🙈

[skjnldsv]

• Set "classmap-authoritative": true inside the config key of composer.json

Seeing this, we can also go for that option and let devs handle this on a case-by-case basis

Maybe this is the way ?
Not touch the workflows but the composer configs ?

[skjnldsv]

Closing then.

@nickvergessen please remove that line from the workflow and move that to the composer.json as a config key :)

[ChristophWurst]

What do we do then see_no_evil

do not follow my lead blindly nextcloud/documentation#10578