Johann150 fba8536743 stop retries after wrong content-type ... It does not make sense to re-request the same resource with the same parameters and expect a different content-type to be returned. Also this makes the error message more sensible and understandable.		2024-02-19 07:50:19 +01:00
..
backend	stop retries after wrong content-type	2024-02-19 07:50:19 +01:00
client	streamline reporting window	2024-02-19 07:46:55 +01:00
foundkey-js	server: remove denormalized note visibility field	2024-01-03 16:13:13 +01:00
shared	disable lint '@typescript-eslint/no-explicit-any'	2023-05-07 14:28:24 +02:00
sw	13.0.0-preview6	2023-07-02 11:13:19 +02:00
meta.json	refactoring	2021-11-12 02:02:25 +09:00