Robert Singer
Robert Singer
That's interesting. I had not considered it. Is there a specific use case you're working on? Might be helpful for us to have something to work backward from.
I think github actions are a good idea, would be nice to have everything integrated within GH. Do you want to do a proof of concept here? On Sun, Feb...
I'm not sure about this. If it's passed in __init__, then it's the initial value so it doesn't seem like it's really changed. There is no prior value. What about...
As you're referencing the `BookSerializer` by string, try including the app name before it like this: ```python expandable_fields = { 'book': ('.BookSerializer', { 'source': 'book' }) } ```
It didn't occur to me that the mixin could call this automatically for the user. Thanks for the input. `scope_queryset` will always be defined because the version in the base...
yep, exactly :)
oh, good point about the breaking change. What do you think about introducing a new mixin called `StrictAccessViewSetMixin` that includes the change and leave the existing mixin as-is?
thanks, I like this. Sorry, behind on this project. Will try to get to soon.
I like the idea of supporting DRF's `SerializerMethodField` as an expandable field. One thing, though, is that it doesn't take keyword arguments for `expand`, `omit`, `fields`. This would only matter...
Thanks, I'm glad you like it :) I've thought about how this could be done a bit in the past, because I've had this use case as well. My idea...