You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the HomePageRequestedReviewsCard & HomePageYourOpenPullRequestsCard are currently up to 100 Pull Requests shown. This can lead to a cluttered Homepage.
Feature Suggestion
To have a more consistent layout on the homepage I would suggest to limit the number of Pull Requests that are initially shown.
This ensures that a card does not take up a lot of height and thus destroy the structure of the homepage.
Possible Implementation
The Spotify HomePageRecentlyVisited & HomePageTopVisited plugins offer the option of configuring how many links should be displayed initially and how many should be loaded after expanding the card. I think this is a good solution to make the layout of the homepage homogeneous and to display the complete content if required.
To follow the example from the Spotify Plugins the Pull Rquest Plugins could offer the following parameters: <HomePageRequestedReviewsCard numPullRequestOpen={5} numPullRequestTotal={50}/>
These parameters can then be used for the GitHub API request: useGithubSearchPullRequest.tsx#L39
Context
This feature would ensure a consistent homepage structure. Furthermore, an OPTIONS and GET request are sent for each repository. The initial limitation also reduces the number of these requests.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
For the
HomePageRequestedReviewsCard
&HomePageYourOpenPullRequestsCard
are currently up to 100 Pull Requests shown. This can lead to a cluttered Homepage.Feature Suggestion
To have a more consistent layout on the homepage I would suggest to limit the number of Pull Requests that are initially shown.
This ensures that a card does not take up a lot of height and thus destroy the structure of the homepage.
Possible Implementation
The Spotify
HomePageRecentlyVisited
&HomePageTopVisited
plugins offer the option of configuring how many links should be displayed initially and how many should be loaded after expanding the card. I think this is a good solution to make the layout of the homepage homogeneous and to display the complete content if required.Example: https://backstage.io/storybook/?path=/story/plugins-home-components-visitedbytype--recently-default
To follow the example from the Spotify Plugins the Pull Rquest Plugins could offer the following parameters:
<HomePageRequestedReviewsCard numPullRequestOpen={5} numPullRequestTotal={50}/>
These parameters can then be used for the GitHub API request: useGithubSearchPullRequest.tsx#L39
Context
This feature would ensure a consistent homepage structure. Furthermore, an OPTIONS and GET request are sent for each repository. The initial limitation also reduces the number of these requests.
The text was updated successfully, but these errors were encountered: