-
Notifications
You must be signed in to change notification settings - Fork 118
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Paginate the commit history page with query params (#1028)
Motivation: It could paginate the commit history page but a page index or a page size is not exposed in query parameters. Because these values were managed only as internal states of Javascript, sharing specific history as a URL was impossible. Modifications: - Update `Breadcrumbs` to specify query parameters - Increase the width of `CompareButton` - Add an option to render a custom component when data is empty in `DynamicDataTable` - Add an option to hide a go-to button in `PaginationBar`. - Expose a browse button when if the path is a directory in `HistoryList` - Refactored `HistoryListPage` to use query parameters to specify revision ranges. - Use a form tag to submit the revision range with an enter key in `ChangesViewPage` - Link to a history page instead of a commit page in a `FileEditor` - Commits for a specific file must be retrieved sequentially from the `HEAD` revision, the Central Dogma server has a limit of 1000 if `maxCommits` is not specified. This means a commit for a specific file is not indexed and may not be found in the recent 1000 commits. - As we can't scan the entire history, it would be better to show the history and guide the user to find a commit rather than failing to find a commit for the file. Result: You can now share a specific range of commit history as a URL.
- Loading branch information
Showing
17 changed files
with
389 additions
and
229 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.