A method for a single page application quoting a remote page component based on configuration

Abstract

A method for a single page application quoting a remote page component based on configuration is disclosed, belonging to the technical field of communications. Specifically, the method has these steps: creating a new public page component development project project, developing the public page component, packaging the public page component, and publishing the public page component to implement thedevelopment and packaging of public page component; then, by acquiring configuration information of a remote page component, generating a dynamic routing according to routing configuration information and visiting the page through the routing to invote the remote page component. The method can synchronously update a plurality of products, reduce the cost of product customization development and make the common page components easier to maintain.

Description

technical field [0001] The invention belongs to the technical field of communication, and in particular relates to a method for referencing a remote page component by a single page application based on configuration. Background technique [0002] Single-page application (SPA) refers to Single Page webApplication, that is, there is only one web page application. A single-page application loads a single html (HyperText Markup Language, HyperText Markup Language) page and dynamically updates it when the user interacts with the application. Pages of web applications. [0003] In the process of loading the page, the browser will first load the necessary html, css (cascading stylesheets, cascading style sheets) and javascript, and all operations are completed on the page controlled by javascript. Single-page applications have the characteristics of rapid release. [0004] Single-page applications also have some disadvantages: Loading a large number of resources for the first time...

AI Technical Summary

Problems solved by technology

[0004] Single-page applications also have some disadvantages: Loading a large number of resources for the first time: when loading for the first time, all front-end resources need to be loaded, and after MVC is front-end, front-end resources will be larger than multi-page applications, and the loading time is relatively long; Not friendly to search engines: single-page applications have only one page, and it is impossible to do SEO for every route

[0007] Furthermore, since the code segmentation of routing pages of single-page applications based on Vue.js is automatically segmented through the import() method, the segmented js page code files will be highly dependent on the current project project. , when the page is displayed by directly referencing this js file, it may not be displayed normally

Therefore, in the customized development of products, it is usually to copy the previous page code with the same function to the new project project, and when the page with the same function has bugs or needs to add functions, it is difficult to communicate between multiple products. Synchronous updates, which will undoubtedly increase the maintenance cost of the product

Images