-
Notifications
You must be signed in to change notification settings - Fork 8
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
include a sample app with one model #27
Comments
Yes, I agree that a default app would be good. I'd probably give it the two models used in the wq.start test suite (location + observation) since that can also demonstrate the client-side foreign key support. As far as not being able to edit, there are supposed to be flags like |
@sheppard Ok so it's a bug then :-) I'm not really sure on which repo to create the issue though ? (wq, or wq.app, or wq.db ?) I get the add/edit functionality when adding |
In this case, the bug is in wq.app. In general, any of the main repos are fine since we can move issues around. |
Hi !
For seasoned Django devs, it's quite straightforward, but it could still be useful to have a very simple
example
app with oneExampleModel
already registered to work out of the box.In my particular case, I couldn't figure out how to make the model editable (despite having all permissions, I can't add new items nor edit existing one from the JS). I guess I missed something in the docs, but it would have been much easier to start with an existing working model.
For advanced users, it's not too much bloat to get rid of (just the whole
example
app folder, and one line in settings.py).Thanks !!
The text was updated successfully, but these errors were encountered: