cloudfoundry / cloudfoundry/stratos
Quota List - Phase two: Be able to compare quotas side by side.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 267
- Forks
- 137
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 77
Description
I think there is two main use cases for the quota list:
-
Managing quotas - this may be selecting one or more quota for deletion, editing or creating quotas.
-
Comparing quotas - side by side comparison allowing users to select the appropriate quota for their needs.
With what we have in progress for quotas we mostly cover use case 1). Use case 2) will need a little bit more work, my initial thoughts are as follows:
-
Convert the quotas list into a table view with only name and creation date/modified date.
-
Allow quotas to be selected with checkboxes.
-
With two or more quotas selected allow the quotas to be shown side by side and compared.
Two initial ideas are (with two or more quotas already selected) a) have a 'compare' button that takes the user to a new comparison page, or b) Once two or more quotas have been selected, automatically bring in a side panel with a comparison component.
I was imagining the quota comparison component being a list with the columns being which ever quotas have been selected, (expanding and shrinking with the users selection) and the rows being all of the various limits and metadata about all of the quotas.
I'm currently leaning towards the b) solution. This solution allows the user to selected and deselect whichever quotas they want.
@vitoravelino What do you think?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing quota list in the TypeScript/Angular UI and read its current selection and metadata rendering. Clarify whether comparison should use a new page or side panel, then define the selected-quota table and completion criteria with maintainers; no file or test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100