nextcloud

트리: f0c367b46c

작성자	SHA1	메시지	날짜
Marcel Klehr	3e6a8b31c4	fix(TextToImage): Fix psalm errors Signed-off-by: Marcel Klehr <mklehr@gmx.net>	8 달 전
Marcel Klehr	e5efbc88d8	enh(TextToImage): Address review comments Signed-off-by: Marcel Klehr <mklehr@gmx.net>	8 달 전
Simon L	d55a7c619d	Fix typos in lib/public subdirectory Found via `codespell -q 3 -S l10n -L jus ./lib/public` Signed-off-by: luz paz <luzpaz@github.com> Update lib/public/Accounts/IAccount.php Signed-off-by: luz paz <luzpaz@github.com> Signed-off-by: Simon L <szaimen@e.mail.de> Co-Authored-By: Côme Chilliet <91878298+come-nc@users.noreply.github.com>	1 년 전
Côme Chilliet	f5c361cf44	composer run cs:fix Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>	1 년 전
John Molakvoæ (skjnldsv)	215aef3cbd	Update php licenses Signed-off-by: John Molakvoæ (skjnldsv) <skjnldsv@protonmail.com>	3 년 전
Christoph Wurst	2c9cdc1cdb	Add our own DB exception abstraction Right now our API exports the Doctrine/dbal exception. As we've seen with the dbal 3 upgrade, the leakage of 3rdparty types is problematic as a dependency update means lots of work in apps, due to the direct dependency of what Nextcloud ships. This breaks this dependency so that apps only need to depend on our public API. That API can then be vendor (db lib) agnostic and we can work around future deprecations/removals in dbal more easily. Right now the type of exception thrown is transported as "reason". For the more popular types of errors we can extend the new exception class and allow apps to catch specific errors only. Right now they have to catch-check-rethrow. This is not ideal, but better than the dependnecy on dbal. Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>	3 년 전

4 커밋 (f0c367b46c2ac8bafc8fdce38cf773dd31b14f2e)