Page History

...

The UI becomes a single independent client-side rendered React application. It will mount once and be fast and easy to navigate around between pages. The React app can handle all of its own asynchronous requests and router management. The UI project can have a modern build process with all the industry-standard developer guide rails. We can remove outdated dependencies like momentjs and bootstrap. This is necessary to truly mark AIP-38 as done.

...

UI REST API

We will refactor our webserver into a Flask REST API with its own OpenAPI spec and generated Swagger docs. This should look very similar to our public REST API with generated types, standard error handling, permission checks, etc. The only difference will be that we don't need to expose this internal API publicly or maintain backward compatibility. The UI should even generate types automatically based on the OpenAPI spec. Full queries and mutations too can be auto-generated anytime the API is changed. A developer can then immediately consume the API in React instead of editing about 4+ files of boilerplate.

...

The default FAB Auth Manager should be replace could be replaced with our own simple auth manager for out-of-the-box development or with a KeyCloak Auth Manager like discussed in AIP-56. KeyCloak brings much more functionality than FAB too Perhaps the FAB Auth Manager can be kept as a provider plugin. That still needs to be explored.

...