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
Most of the forms can be ported to React as they only available to authenticated (and in most cases to a privileged) users. We will get the following benefits:
features will be decoupled on HTTP level (see also Split packages by features #927, Split code to Maven modules #1002). For example, SeriesController is coupled with country, category, sales, participants and collection only because we need to show this information on series info page. With React, the components will load all required information via HTTP.
completely removes an issue where we have to invalidate pages of authenticated users as there might be some sensitive data. With React components, the page content is always the same and only some parts are loading when needed. The permitions to load the parts can be constrained by URLs.
it also helps in introduction of microservices (Split to microservices #1162) as React components will load data via API.
We can't transform it to a fully Single Page Application (SPA) as some pages should be available to search engine bots but all the interactive pages can be partially or fully moved to React.
As frontend is developed independently from backend, we should have a toggle to keep the components
switched off until we have API.
Part of #1328
[skip ci]
Most of the forms can be ported to React as they only available to authenticated (and in most cases to a privileged) users. We will get the following benefits:
We can't transform it to a fully Single Page Application (SPA) as some pages should be available to search engine bots but all the interactive pages can be partially or fully moved to React.
This task depends on:
The text was updated successfully, but these errors were encountered: