-
Notifications
You must be signed in to change notification settings - Fork 7
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
Support views with no model #56
Comments
wisersoftwareengineer
added a commit
to wisersoftwareengineer/worf
that referenced
this issue
Mar 27, 2023
- test written to simulate a view with a dummy model to validate the scenario
wisersoftwareengineer
added a commit
to wisersoftwareengineer/worf
that referenced
this issue
Mar 27, 2023
- Increasing the test scenarios
wisersoftwareengineer
added a commit
to wisersoftwareengineer/worf
that referenced
this issue
Mar 27, 2023
- Created a workaround to user a fake model - updated documentation explaining how to use it
wisersoftwareengineer
added a commit
to wisersoftwareengineer/worf
that referenced
this issue
Mar 27, 2023
- Created a workaround to user a fake model - updated documentation explaining how to use it
wisersoftwareengineer
added a commit
to wisersoftwareengineer/worf
that referenced
this issue
Mar 27, 2023
- using a custom serializer to have an example for the users
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Worf currently raises
ImproperlyConfigured
ifmodel
is set to the default value ofNone
, butNone
should probably be supported.If you set
model
to something else likeFalse
it then falls down when trying to build the filterset:Supplying your own queryset via
get_queryset
or response viaget
both bypass the need for a model which is handy in certain cases, currently the only way to suppress the error is to pass a model e.g. thedjango.db.models.Model
abstract, even though it isn't used for anything meaningful.The text was updated successfully, but these errors were encountered: