Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Use nested namespaces #92

Closed
rolandgeider opened this issue Sep 24, 2014 · 0 comments
Closed

Use nested namespaces #92

rolandgeider opened this issue Sep 24, 2014 · 0 comments
Assignees
@rolandgeider
Labels
effort: high High effort/complexity, e.g. big feature
Milestone
1.5

Comments

@rolandgeider
Copy link
Member

Many of the urls.py files could be simplified by using nested namespaces, e.g. 'core:license:list' instead of 'core:license-list'
@rolandgeider rolandgeider added effort: high High effort/complexity, e.g. big feature bitesize labels Sep 24, 2014
@rolandgeider rolandgeider self-assigned this Sep 24, 2014
rolandgeider added a commit that referenced this issue Sep 27, 2014
@rolandgeider
Use nested namespaces for gym URLs
fdc3500 
See #92
rolandgeider added a commit that referenced this issue Nov 18, 2014
@rolandgeider
Use nested namespaces for exercise URLs
a3cd62b 
See #92
rolandgeider added a commit that referenced this issue Nov 18, 2014
@rolandgeider
Use nested namespaces for nutrition URLs
5952366 
See #92
rolandgeider added a commit that referenced this issue Nov 19, 2014
@rolandgeider
Use nested namespaces for configuration URLs
d5796a6 
See #92
rolandgeider added a commit that referenced this issue Nov 19, 2014
@rolandgeider
Use nested namespaces for core URLs
51e6938 
See #92
rolandgeider added a commit that referenced this issue Nov 20, 2014
@rolandgeider
Use nested namespaces for manager URLs
bd30410 
See #92
@rolandgeider rolandgeider added this to the 1.5 milestone Nov 20, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rolandgeider rolandgeider

Labels
effort: high High effort/complexity, e.g. big feature
Projects
None yet
Milestone
1.5
Development

No branches or pull requests
1 participant
@rolandgeider