cloudfoundry / cloudfoundry/stratos
Lists: "No x for current filter" message shown incorrectly.
Open
Nobody has claimed this yet.
bug
- Dominant language
- TypeScript
- Stars
- 267
- Forks
- 137
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 77
Description
Theory:
- This applies to CF lists that have the CF, org, space drop down filters.
- Only when a single CF is connected.
With no other other filters applied and no results the list incorrectly shows the "No x for current filter" message rather than the "No results" message. This is only the case when only one CF is connected.
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
Reproduce the issue in a CF list with a single connected CF, using the org and space dropdown filters with no other filters applied. Trace the list's empty-state handling and verify that no results shows the "No results" message, while an active filter with no matches shows "No x for current filter."
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100