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.

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

Limit ranges frontend #1285

Closed
wants to merge 1 commit into from

Conversation

batikanu
Copy link
Contributor

Implementation of Limit ranges frontend.
It includes also small fixes in backend.

@codecov-io
Copy link

codecov-io commented Sep 26, 2016

Current coverage is 93.85% (diff: 96.73%)

Merging #1285 into master will increase coverage by 0.08%

@@             master      #1285   diff @@
==========================================
  Files           342        355    +13   
  Lines          3080       3171    +91   
  Methods           0          0          
  Messages          0          0          
  Branches          0          0          
==========================================
+ Hits           2888       2976    +88   
- Misses          192        195     +3   
  Partials          0          0          

Powered by Codecov. Last update 8417b4f...c8300e4

@floreks
Copy link
Member

floreks commented Sep 30, 2016

'Limit Ranges' section is missing on admin page. Please add.

@batikanu batikanu force-pushed the limitranges-frontend branch 2 times, most recently from ab1f443 to 09fb8f0 Compare September 30, 2016 13:03
@batikanu
Copy link
Contributor Author

'Limit Ranges' section is added on admin page. PTAL

@batikanu batikanu force-pushed the limitranges-frontend branch from 09fb8f0 to 2ee815e Compare September 30, 2016 13:36
Copy link
Contributor

@bryk bryk left a comment

Choose a reason for hiding this comment

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

Hmm... Can you show a couple of screenshots here? Should this be added to top level navigation or just as a property of a namespace?

I'm concerned about this because I think it does not make sense to look at a limit range alone. A limit range always belongs to exactly one namespace.

What do you think?

@batikanu
Copy link
Contributor Author

batikanu commented Oct 7, 2016

@bryk I think it should be like resource quotas only in namespace details. I will move limit range detail to namespace detail and post some screen shots.

@batikanu batikanu force-pushed the limitranges-frontend branch from 2ee815e to c8300e4 Compare October 7, 2016 09:14
@bryk
Copy link
Contributor

bryk commented Oct 7, 2016

@batikanu Awesome, thanks!

@batikanu batikanu closed this Oct 12, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants