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
Attempting to implement various requested features in APIView have many times proved difficult or impossible. Most of these are due to the current architecture of APIView and others are limitations in ASP.NET MVC framework. For a while I have been exploring way to rearchitect APIView such that many of these features can be implemented in a robust non-hacky manner. This issue explains the coming changes and a timeline for completing them.
The main idea is to decouple the presentation code from most of the logic by exposing a robust APIView API (this is one of our user requests), then replacing the client side with a progressive web application that offers many tools for modern and rapid web development out of the box. The goal here is that the API would be as useful as the client application such that one could potentially build a different client (say VS code) to run off it or just use the API directly. The PWA front end will run side by side with existing ASP.NET until we decide to retire the later.
A lot of this work is already done. Below is a time frame for completion.
Index Page , Review & APIRevison API endpoint - Completed Not deployed. Issues Resolved
Review Page, API endpoint for APITree Tokens, and Comments, Approval e.t.c. Issues Resolved
The main issue that will be addressed here is the addition of true lazy loading so we don't experience page performance issue when loading documentation or packages with large number of APIs.
We also enable many features request that we cannot currently implement properly due to limitations of UI components of native ASP.Net MVC.
Requests from Feedback Session May 23rd 2024
Pinned APIRevision (Latest GA, Latest Approved, Current Main, Latest Released). Shown as regular dropdown items with appropriate tags, pinned to the top of the dropdown list.
Re-Order filters in API Revision Select: Approved, Released, Auto, Manual, PR.
Use Auto, Manual, PR Icons on filter buttons and add tooltip over icons.
Add Diff styles. Full Diff (Full API with diff shown), Tree Diff (Only nodes with diff in descendant but show full content), Node Diff (Only nodes with diff in descendant but show only the nodes with diff and some context around them).
What's required to Deploy to Production
This will be made available on language basis with C# and Java being the first
Script run against original files to generate tree style tokens stored alongside flat list of tokens.
Update Automatic and Pull Request API to support tree tokens. (Basically, Comparing API Revisions to evaluate if there is a change)
Feature Parity with regular APIView. Approval, Request Reviewers, Subscribe, Mark as Viewed, Change History Display, Navigation Jumps
Sample Page - Completed at later date
The content you are editing has changed. Please copy your edits and refresh the page.
Attempting to implement various requested features in APIView have many times proved difficult or impossible. Most of these are due to the current architecture of APIView and others are limitations in ASP.NET MVC framework. For a while I have been exploring way to rearchitect APIView such that many of these features can be implemented in a robust non-hacky manner. This issue explains the coming changes and a timeline for completing them.
The main idea is to decouple the presentation code from most of the logic by exposing a robust APIView API (this is one of our user requests), then replacing the client side with a progressive web application that offers many tools for modern and rapid web development out of the box. The goal here is that the API would be as useful as the client application such that one could potentially build a different client (say VS code) to run off it or just use the API directly. The PWA front end will run side by side with existing ASP.NET until we decide to retire the later.
A lot of this work is already done. Below is a time frame for completion.
Index Page , Review & APIRevison API endpoint - Completed Not deployed.
Issues Resolved
Review Page, API endpoint for APITree Tokens, and Comments, Approval e.t.c.
Issues Resolved
Requests from Feedback Session May 23rd 2024
What's required to Deploy to Production
This will be made available on language basis with C# and Java being the first
Required to close the epic
Other issues to keep in mind while working on this
@maririos @praveenkuttappan @JonathanGiles
The text was updated successfully, but these errors were encountered: