SD

In reality if you google this topic extensively, you'll notice that there are a number of ways to tackle it. In the example below, the path we've chosen is to...

I disagree with the Graphene vs Strawberry parity remark @thclark. Recently doing a large project with strawberry, I've mainly found it to be a steep learning curve with some rough...

I have some thoughts on the matter yes. This was actually something I've been working on inside our OneSila project. How I solved it, from memory: -> A model subscription...

@thclark just had some time to go through the code. How I solved this inside OneSila is not by hooking the subscriptions into the mutations. Instead leveraging Django's nice signal-system,...

@thclark Glad you like it. It took good bit of R&D / Deep diving into the lib to get there. Overall it was designed to be usable with minimal effort...

Sounds you want to hammer that out in the backend to ensure you cannot fetch non-related info from the frontend. In [Onesila.com](https://www.onesila.com) we wanted to ensure all information is attached...

You really want to go more upstream and filter it at the deepest level where you have access to both the data and logged in user. That's why in the...

The main change is the usage of objects.create() rather than setting an instance and then saving it. It is correct that the dummy-instance still has that old behaviour, but the...

@tokr-bit I would appreciate this fix. I feel this would be something I'd run into myself as well during my project.

I do, see below: ``` Client matching query does not exist. GraphQL request:2:3 1 | mutation createClient{ 2 | createClient(data:{name: "client"}){ | ^ 3 | name Traceback (most recent call...