-
Notifications
You must be signed in to change notification settings - Fork 189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New device auto set active=False #53
Comments
Just a side note,
In case |
Why would you pass that as extra kwargs if it's already defaulted to active? |
I'm also facing same issue. @xtrinch extra kwargs sets active to true using below code. in but So I think below code might need some changes
So when I removed
Then it works. If you are agree with this change, I would love to make pull request. |
I'm also experiencing this issue on the latest version 0.2.19. |
Fix issue #53 - default active bug in DRF views
Hi,
I'm getting a weird issue, can't seem to find out the reason why, as the default value in device model of active field is set to True.
However when I try to create a new device (without explicitly pass
active
),active
is automatically set to False.Seems like
extra_kwargs = {"active": {"default": True}}
doesn't work as expected. Only whenactive
is added toread_only_fields
then it works.Anyone get the same issue?
Thanks
The text was updated successfully, but these errors were encountered: