selfprivacy-rest-api/selfprivacy_api/graphql/mutations
Inex Code b78ee5fcca refactor(api): Group mutations
I've learned that there is no problem in grouping mutations like we do with queries.
This is a big mistake from my side, now we have legacy not so conveniently placed endpoints.
I've grouped all mutations, left the copies of old ones flattened in the root for backwards compatibility.
We will migrate to mutation groups on client side, and backups now only use grouped mutations.
Tests are updated.
2023-07-17 16:05:00 +03:00
..
__init__.py API keys graphql tests 2022-06-29 20:39:46 +03:00
api_mutations.py refactor(tokens-repo): do not use tokens repo directly from graphql 2022-12-26 14:13:46 +00:00
backup_mutations.py refactor(api): Group mutations 2023-07-17 16:05:00 +03:00
deprecated_mutations.py refactor(api): Group mutations 2023-07-17 16:05:00 +03:00
job_mutations.py refactor: Use singleton metaclass for all singleton classes 2022-10-27 18:31:52 +03:00
mutation_interface.py refactor(api): Group mutations 2023-07-17 16:05:00 +03:00
services_mutations.py refactor(api): Group mutations 2023-07-17 16:05:00 +03:00
storage_mutations.py refactor(api): Group mutations 2023-07-17 16:05:00 +03:00
system_mutations.py Migrate to FastAPI (#13) 2022-08-25 20:03:56 +03:00
users_mutations.py refactor(api): Group mutations 2023-07-17 16:05:00 +03:00