This RFC proposes adding support for navigating to the "next" and "previous" package.
While packages do not have an inherent order, allowing easier navigation between packages allows users to explore the project more readily.
The concept of navigating to the "next" and "previous" API is found elsewhere (e.g., see NumPy's sin).
This should be a straightforward addition. Will require loading a list of packages and tracking the index of the currently active package within that list.
Description
This RFC proposes adding support for navigating to the "next" and "previous" package.
While packages do not have an inherent order, allowing easier navigation between packages allows users to explore the project more readily.
The concept of navigating to the "next" and "previous" API is found elsewhere (e.g., see NumPy's sin).
This should be a straightforward addition. Will require loading a list of packages and tracking the index of the currently active package within that list.
Related Issues
No.
Questions
No.
Other
No.
Checklist
RFC:
.