Usually Nextcloud DI goes through constructor injection. This has the implication that each instance of a class builds the full DI tree. That is the injected services, their services, etc. Occasionally there is a service that is only needed for one controller method. Then the DI tree is build regardless if used or not. If services are injected into the method, we only build the DI tree if that method gets executed. This is also how Laravel allows injection. Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at> |
1 year ago | |
---|---|---|
.. | ||
Bootstrap | Add event logging to app loading | 2 years ago |
Controller | Adds a "Request password" button to the public share authentication page for shares | 2 years ago |
Db | Remove long depreated AppFramework/Db/Mapper | 1 year ago |
DependencyInjection | Adjust and add unit tests | 2 years ago |
Http | feat(app framework)!: Inject services into controller methods | 1 year ago |
Middleware | use bruteforce protection on all methods wrapped by PublicShareMiddleware | 1 year ago |
OCS | Format control structures, classes, methods and function | 4 years ago |
Routing | Remove at matcher uses in tests/lib | 2 years ago |
Utility | Format code to a single space around binary operators | 3 years ago |
AppTest.php | Add a built-in profiler inside Nextcloud | 2 years ago |