Skip to content
This repository has been archived by the owner on Mar 28, 2019. It is now read-only.

Organize code into a resource module #490

Merged
merged 1 commit into from
Oct 22, 2015
Merged

Organize code into a resource module #490

merged 1 commit into from
Oct 22, 2015

Conversation

leplatrem
Copy link
Contributor

  • Group resource, viewset, schema into a resource module. Since all this is optional to use.
  • Rename Collection to Model, since it is what it is :)
  • Document
  • Support deprecation

@Natim @ametaireau thoughts ?

@@ -0,0 +1 @@
from .base import *
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should not import * there, either move the base code here or define the __all__ variable.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes ok, but what do you think of the overall move ?

@leplatrem
Copy link
Contributor Author

Ready to review !

@Natim
Copy link
Contributor

Natim commented Oct 22, 2015

It looks good to me.

@leplatrem leplatrem modified the milestone: 2.9 Oct 22, 2015
leplatrem added a commit that referenced this pull request Oct 22, 2015
Organize code into a resource module
@leplatrem leplatrem merged commit f4ae4af into master Oct 22, 2015
@leplatrem leplatrem deleted the resource-module branch October 22, 2015 10:21
glasserc pushed a commit that referenced this pull request May 20, 2016
glasserc pushed a commit that referenced this pull request May 20, 2016
glasserc pushed a commit that referenced this pull request May 20, 2016
Do not always start with reload option (fixes #490)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants