Register services early in case they might already be queried though other registrations

[juliusknorr]

Otherwise services might not be resolved since they are registered too late

[ChristophWurst]

🤔 where is that a problem? Shouldn't the registration part be as lazy as possible? Like in a sense that nothing really is executed yet.

[juliusknorr]

thinking where is that a problem? Shouldn't the registration part be as lazy as possible? Like in a sense that nothing really is executed yet.

Ideally yes, just found this when debugging nextcloud/deck#2275 and thought it might be a good hardening to avoid possible issues in case app developers don't properly handle lazy registration like myself ;)

[ChristophWurst]

At this very early stage of the process lifetime, no other apps nor all of the server components are ready. Therefore the app must not try to use anything except the API provided by the context.

https://docs.nextcloud.com/server/latest/developer_manual/app_development/bootstrap.html#nextcloud-20-and-later

🙈 so I would not see this as a hardening step. The premise of of the register and boot separation is to not have any assumptions about what's there in the early call of register.

[ChristophWurst]

👎 as of #22727 (comment) :)

[juliusknorr]

Ok, let's close then 👍