You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to django-piston
I came to discover that if i don't tie a model to my resource , the
generated documentation does not show up for that resource. So the
easiest thing to do was to add a model to to the resource. But having
more resources with the same model will get me in trouble. My tests
fail , piston apparently does not know which resource it should use
for a model instance.
Is it some design thing I'm missing here? Should I inherit from a
resource with a model?
Or should the docs generator be fixed to also include those resources
without a model?
I looked into the source, the docs generator uses a dict generated by
the type mapper class. Which checks if a handler has a model
attribute. So no model attribute means no generated documentation.
Stephan
jespern
unread,
Jul 30, 2009, 3:45:57 AM7/30/09
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to django-piston
This is basically just lacking from the documentation generation code.
We should of course also include non-model resources.
Feel free to expand upon it, as I won't have time to do it in a near
future.