Content
View differences
Updated by Jan Sandbrink 7 months ago
**As** a user
**I want to** load fewer projects into the project selector and load them asynchronously,
**so that** the project selector doesn't feel sluggish when dealing with a large number of projects.
**Acceptance criteria**
* Only load 200 projects at once
* Entering a search term, will search across all projects and show up to 200 of them
* to be confirmed: When the user scrolls to the bottom of the list, a link is shown: "Show more projects"
* The link leads to the project list (`/projects`)
* The linked project list is prefiltered according to the current search term
* to be confirmed: When opening the project selector while in a project, the selector opens with the given project selected
**Background**
The current behaviour of the project selector is as follows:
1. Show a skeleton loader, as long as loading projects has not finished
2. Load **all** projects (even if it's ten thousands and multiple network requests are necessary)
3. Perform all filtering locally
* which can feel sluggish for many projects as well
**I want to** load fewer projects into the project selector and load them asynchronously,
**so that** the project selector doesn't feel sluggish when dealing with a large number of projects.
**Acceptance criteria**
* Only load 200 projects at once
* Entering a search term, will search across all projects and show up to 200 of them
* to be confirmed: When the user scrolls to the bottom of the list, a link is shown: "Show more projects"
* The link leads to the project list (`/projects`)
* The linked project list is prefiltered according to the current search term
*
**Background**
The current behaviour of the project selector is as follows:
1. Show a skeleton loader, as long as loading projects has not finished
2. Load **all** projects (even if it's ten thousands and multiple network requests are necessary)
3. Perform all filtering locally
* which can feel sluggish for many projects as well