List data processing method, system and device, medium and program product
By building module sequences and asynchronous placeholder components, dynamic rendering of long list data is solved, and the problem of not being able to adapt to dynamic scenario-based needs in the existing technology is achieved, adaptive display and functional consistency under different devices and screen sizes are achieved, memory and traffic consumption are reduced, and user experience is improved.
Patent Information
- Application Number
- CN202510616948.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-05-14
- Publication Date
- 2025-08-12
AI Technical Summary
When facing the demand for dynamic scenarios, existing long list technology cannot be flexibly adjusted, resulting in poor user experience, unable to adapt to different devices or screen sizes, and unable to display data items and layouts in a targeted manner, making it difficult to adapt to the development requirements of modern web and mobile applications.
By obtaining the basic element information and insert element information of the list data, a module sequence is built, and asynchronous placeholder components are built based on the insertion position parameters. Combined with lazy loading technology, the module sequence is dynamically rendered, ensuring that core functions are preferred and redundant requests and rendering overhead is reduced.
It realizes flexible component insertion and hiding according to the needs of the scenario, ensures functional consistency in different scenarios, reduces memory usage and traffic consumption, and improves user experience.
Smart Images
Figure CN120470192A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the technical field of list data processing, and in particular to a list data processing method, system, device, medium and program product. Background Art
[0002] In today's digital age, modern web and mobile applications are widely used in various fields. Long lists, as common user interface components, play a key role in presenting users with rich information by displaying a large number of data items. However, with the development of applications, the amount of data has exploded, and users' expectations for interaction have become increasingly complex and diverse. Traditional long list technologies have exposed many drawbacks.
[0003] Existing long list technologies typically employ static construction and rendering methods, making them difficult to adapt to dynamic scenarios. In this static model, list content and layout are determined at the outset and cannot be flexibly adjusted to different states and scenarios. For example, when data is updated, the list cannot be dynamically refreshed to display the latest data; the list layout cannot adapt to different devices or screen sizes, affecting the user experience; and the list layout cannot be displayed specifically for different user permissions or business process states. This limits its applicability in complex application environments and makes it difficult to adapt to the dynamic development requirements of modern web and mobile applications. Summary of the Invention
[0004] The technical problem to be solved by the present disclosure is to overcome the defect of inflexible list data processing in the prior art and to provide a list data processing method, system, device, medium and program product.
[0005] The present disclosure solves the above technical problems through the following technical solutions:
[0006] In a first aspect, a method for processing list data is provided, the processing method comprising:
[0007] In response to a request to load list data, acquiring basic element information and inserted element information of the list data;
[0008] Wherein, the insertion element information includes insertion position parameters;
[0009] Constructing a module sequence of the list data based on the basic element information;
[0010] Constructing an asynchronous placeholder component based on the insertion element information, and listing the asynchronous placeholder component in the module sequence using the insertion position parameter;
[0011] Renders the module sequence.
[0012] Optionally, the step of rendering the module sequence includes:
[0013] Obtaining the loading status of each module in the module sequence in real time;
[0014] Based on the mapping relationship between the loading status corresponding to each module and the corresponding module, the module sequence is dynamically rendered.
[0015] Optionally, the step of dynamically rendering the module sequence based on the mapping relationship between the loading status corresponding to each module and the corresponding module includes:
[0016] In response to the loading state of the module being characterized as an initialization state, rendering the corresponding module using a rendering skeleton screen; and / or,
[0017] In response to the loading state of the module being characterized as a loading state and the position of the module being at the top of the viewport, performing ceiling rendering on the module; and / or,
[0018] In response to the module loading status being characterized as a loading success status, rendering the list data; and / or,
[0019] In response to the loading status of the module being characterized as the interface returning a no-data state, a corresponding empty state prompt is displayed.
[0020] Optionally, the insertion element information further includes a list matching parameter corresponding to the insertion position parameter, and the step of constructing an asynchronous placeholder component based on the insertion element information includes:
[0021] Identifying the type of the list data;
[0022] determining the list matching parameter based on the type of the list data;
[0023] The insertion position parameter corresponding to the list matching parameter is obtained.
[0024] Optionally, the insertion element information includes map information, the basic element information includes a fixed page header, and the step of listing the asynchronous placeholder component in the module sequence using the insertion position parameter includes:
[0025] In response to the type of the list data being the first map scene, splitting the fixed header into tabs and filters;
[0026] Constructing a first asynchronous placeholder component using the map information, and inserting the first asynchronous placeholder component between the tab and the filter;
[0027] In response to the type of the list data being the second map scene, writing a map display / hidden flag into the additional configuration of the fixed page header;
[0028] Constructing a second asynchronous placeholder component using the map information, and inserting the second asynchronous placeholder component below the fixed header;
[0029] Displaying the second asynchronous placeholder component based on the map visibility flag;
[0030] The display range of the first asynchronous placeholder component is larger than that of the second asynchronous placeholder component.
[0031] Optionally, the inserted element information further includes hotel recommendation information, the basic element information includes a fixed header and a header notification component, and the step of listing the asynchronous placeholder component in the module sequence using the insertion position parameter includes:
[0032] In response to the type of the list data being a hotel external projection scenario, splitting the fixed header into tabs and filters;
[0033] A third asynchronous placeholder component is constructed using the hotel recommendation information, and the tab, the page header notification component, the third asynchronous placeholder component, and the filter are arranged in sequence.
[0034] In a second aspect, a system for processing list data is provided, the processing system comprising a data acquisition module, a list construction module, an asynchronous insertion module, and a rendering module;
[0035] The data acquisition module is configured to acquire basic element information and inserted element information of the list data in response to a request to load the list data;
[0036] Wherein, the insertion element information includes insertion position parameters;
[0037] The list construction module is used to construct a module sequence of the list data based on the basic element information;
[0038] The asynchronous insertion module is configured to construct an asynchronous placeholder component based on the insertion element information, and list the asynchronous placeholder component in the module sequence using the insertion position parameter;
[0039] The rendering module is used to render the module sequence.
[0040] In a third aspect, an electronic device is provided, comprising a memory, a processor, and a computer program stored in the memory and configured to run on the processor, wherein the processor implements the method for processing list data as described in the first aspect when executing the computer program.
[0041] In a fourth aspect, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the method for processing list data as described in the first aspect is implemented.
[0042] The fifth party provides a computer program product, including a computer program, which, when executed by a processor, implements the method for processing list data as described in the first aspect.
[0043] On the basis of conforming to the common sense in this field, the above-mentioned preferred conditions can be arbitrarily combined to obtain the preferred embodiments of the present disclosure.
[0044] The positive progress of this disclosure lies in: dynamically obtaining module configuration information through asynchronous interfaces based on scenario requirements, flexibly inserting or hiding components, and asynchronously loading key modules to ensure that core functions are displayed first, avoiding blocking the first screen rendering due to complex content, while ensuring functional consistency in different scenarios. Specific modules are loaded only when necessary, reducing redundant requests and rendering overhead. In combination with lazy loading technology, non-visible areas in long lists are loaded lazily, reducing memory usage and data consumption. BRIEF DESCRIPTION OF THE DRAWINGS
[0045] Figure 1 A flowchart of a method for processing list data provided by an exemplary embodiment of the present disclosure;
[0046] Figure 2 This is a flowchart of step S104 in a method for processing list data provided by an exemplary embodiment of the present disclosure;
[0047] Figure 3 This is a flowchart of step S103 in a method for processing list data provided by an exemplary embodiment of the present disclosure;
[0048] Figure 4 A module diagram of a system for processing list data provided by an exemplary embodiment of the present disclosure;
[0049] Figure 5 A schematic diagram of the hardware structure of an electronic device provided by an exemplary embodiment of the present disclosure. DETAILED DESCRIPTION
[0050] The present disclosure is further illustrated below by way of examples, but the present disclosure is not limited to the scope of the examples.
[0051] In the embodiments of the present disclosure, prefixes such as "first" and "second" are used only to distinguish different description objects, and have no limiting effect on the position, order, priority, quantity or content of the described objects. In the embodiments of the present disclosure, the use of prefixes such as ordinal numbers to distinguish description objects does not constitute a limitation on the described objects. For the statement of the described objects, please refer to the description in the context of the claims or embodiments, and no unnecessary limitations should be constituted due to the use of such prefixes. In addition, in the description of this embodiment, unless otherwise specified, the meaning of "plurality" is two or more.
[0052] In the embodiments of the present disclosure, the collection, storage, use, processing, transmission, provision and disclosure of user personal information involved comply with the provisions of relevant laws and regulations and do not violate public order and good morals.
[0053] Example 1
[0054] Figure 1 A flowchart of a method for processing list data provided by an exemplary embodiment of the present disclosure, the processing method comprising:
[0055] S101. In response to a request to load list data, obtain basic element information and inserted element information of the list data;
[0056] Wherein, the insertion element information includes insertion position parameters;
[0057] Specifically, the basic element information includes basic information such as ID, title or content and style information, and the inserted element information is obtained using an asynchronous interface.
[0058] S102: Construct a module sequence of the list data based on the basic element information;
[0059] Specifically, we build basic data modules based on basic element data. For each built basic data module, we enumerate all possible module types, such as "product card," "advertising module," "loading prompt," "empty state," and "error prompt," according to business needs. Based on the state information, we decide which type of module to generate.
[0060] The method for defining the generation of UI basic data is as follows:
[0061] generListData(cardType: CommonListDataType, extra = null) {
[0062] return { cardType, extra} as ITheAgedClubProductType<typeof extra> ;
[0063] }
[0064] By defining the basic data module, the UI module can be placed directly into the extra extended data when special data processing is required.
[0065] S103: construct an asynchronous placeholder component based on the insertion element information, and list the asynchronous placeholder component in the module sequence using the insertion position parameter;
[0066] Specifically, use the module generator function to dynamically generate different list modules based on status and data.
[0067] S104: Render the module sequence.
[0068] In this solution, module configuration information is dynamically retrieved through asynchronous interfaces based on scenario requirements, allowing for flexible insertion or hiding of components. Key modules are asynchronously loaded to prioritize core functionality, preventing complex content from blocking the initial rendering screen while ensuring functional consistency across different scenarios. Specific modules are loaded only when necessary, reducing redundant requests and rendering overhead. Lazy loading technology is also used to delay the loading of non-visible areas in long lists, reducing memory usage and data consumption.
[0069] As a feasible way, Figure 2 As shown, step S104 includes:
[0070] S1041. Acquire the loading status of each module in the module sequence in real time;
[0071] Specifically, the loading status includes page initialization loading status (init), page loading status (loading), page loading more status (pageLoading), loading success status (success), request no result status (empty), and request no more data status (nomore).
[0072] S1042: Dynamically render the module sequence based on the mapping relationship between the loading status corresponding to each module and the corresponding module.
[0073] Specifically, if the loading status is "loading", a placeholder module is generated to display the loading animation; if the loading status is "empty data", a specific module is generated to prompt the user that "no data yet"; if the loading status is "no more data", a module is generated to prompt the user that "no more content"; if the loading status is "normal data", a basic data module is generated to display the actual content.
[0074] In this solution, the page dynamically adjusts the rendering logic of different modules based on the mapping relationship between loading status and module type. The page can dynamically generate modules based on the return results of data requests, respond to user interaction behaviors in real time, and ensure a smooth user experience.
[0075] As an implementable manner, step S1042 includes:
[0076] In response to the loading state of the module being characterized as an initialization state, rendering the corresponding module using a rendering skeleton screen;
[0077] Specifically, in the page initialization loading state (init), build the skeleton screen module of the corresponding module, such as [HeaderSkeleton (top skeleton screen), ProductSkeleton (product skeleton screen)], generate the list module and render it;
[0078] and / or,
[0079] In response to the loading state of the module being characterized as a loading state and the position of the module being at the top of the viewport, performing ceiling rendering on the module;
[0080] Specifically, when the page is loading, build the ceiling rendering of the corresponding top module, such as [StickyHeader (fixed header component), HeaderTip (top tab), ProductSkeleton (product skeleton screen)], and render the top of the ceiling and the corresponding product list skeleton screen.
[0081] and / or,
[0082] In response to the module loading status being characterized as a loading success state, rendering the list data;
[0083] Specifically, in the successful loading state (success), the corresponding rendering is performed based on the module sequence of the list data, such as [StickyHeader (fixed header component), HeaderTip (top tab), Product1 (product component 1), Product2 (product component 2), ...].
[0084] and / or,
[0085] In response to the loading status of the module being characterized as the interface returning a no-data state, a corresponding empty state prompt is displayed.
[0086] Specifically, when the request has no result (empty) or no more data (nomore), the corresponding prompt page is rendered.
[0087] In this solution, the skeleton screen module is used during the initial loading state of the page to quickly provide visual feedback, preventing users from seeing a blank page or prolonged unresponsiveness during the loading process. Rendering the modules at the top of the viewport ensures that key modules remain within the user's field of view, allowing them to easily operate or reference them at any time. When the interface returns no data, displaying the corresponding empty state prompt clearly informs users that the current page has no content to display, preventing users from misunderstanding the page's functionality.
[0088] As an implementable manner, the insertion element information further includes a list matching parameter corresponding to the insertion position parameter, such as Figure 3 As shown, the step of constructing an asynchronous placeholder component based on the inserted element information in step S103 includes:
[0089] S1031, identifying the type of the list data;
[0090] S1032. Determine the list matching parameter based on the type of the list data;
[0091] S1033. Obtain the insertion position parameter corresponding to the list matching parameter.
[0092] In this solution, business scenarios are matched with list data of corresponding types according to business needs, and insertion rules are decoupled from data types. When adding new data types, it is only necessary to supplement the mapping relationship between types and parameters without modifying existing code. By determining the insertion position of the inserted element in the current type of list data, automatic matching of rule parameters is achieved, ensuring that the logic of the inserted element is highly consistent with the list data content, and flexible adaptation to complex business scenarios.
[0093] As an implementable manner, the inserted element information includes map information, the basic element information includes a fixed header, and the step of including the asynchronous placeholder component in the module sequence using the insertion position parameter in step S103 includes:
[0094] In response to the type of the list data being the first map scene, splitting the fixed header into tabs and filters;
[0095] Constructing a first asynchronous placeholder component using the map information, and inserting the first asynchronous placeholder component between the tab and the filter;
[0096] In response to the type of the list data being the second map scene, writing a map display / hidden flag into the additional configuration of the fixed page header;
[0097] Constructing a second asynchronous placeholder component using the map information, and inserting the second asynchronous placeholder component below the fixed header;
[0098] Displaying the second asynchronous placeholder component based on the map visibility flag;
[0099] The display range of the first asynchronous placeholder component is larger than that of the second asynchronous placeholder component.
[0100] In this solution, the map display range within the scenario determines whether the business scenario belongs to the primary map scenario of the large map or the secondary map scenario of the small map. In the large map scenario, by splitting the tabs and filters into independent modules, the preferred map display area is inserted, while maintaining the display consistency of the map and filter conditions, ensuring smooth information display during map operations. For the small map scenario, modules are merged to reduce the top viewport area, and the map visibility flag (isShowMap) is used to dynamically adjust the layout weight and balance information density.
[0101] As an implementable manner, the inserted element information further includes hotel recommendation information, the basic element information includes a fixed header and a header notification component, and the step of listing the asynchronous placeholder component in the module sequence using the insertion position parameter includes:
[0102] In response to the type of the list data being a hotel external projection scenario, splitting the fixed header into tabs and filters;
[0103] A third asynchronous placeholder component is constructed using the hotel recommendation information, and the tab, the page header notification component, the third asynchronous placeholder component, and the filter are arranged in sequence.
[0104] This solution utilizes a modular architecture to decouple the functionality of list data. The sequential arrangement of tabs, header notifications, recommendation components, and filters aligns with the user's natural flow from browsing to filtering. Hotel recommendation information is built as a separate asynchronous component, allowing for delayed loading without impacting the main workflow, ensuring a fast first-screen response. Users can use tabs to switch categories or filter hotels immediately upon page load, without having to wait for recommendations to load. Hotel recommendation information includes HotelOutTitle (external collaboration title) and / or Recommendation (recommendation information).
[0105] The list data processing method provided in this embodiment dynamically obtains module configuration information through an asynchronous interface according to scenario requirements, flexibly inserts or hides components, and asynchronously loads key modules to ensure that core functions are displayed first, avoiding blocking the first screen rendering due to complex content, while ensuring functional consistency in different scenarios. Specific modules are loaded only when necessary, reducing redundant requests and rendering overhead. In combination with lazy loading technology, non-visible areas in long lists are loaded lazily, reducing memory usage and data consumption.
[0106] Example 2
[0107] Corresponding to the aforementioned embodiment of the method for processing list data, the present disclosure also provides an embodiment of a system for processing list data.
[0108] Figure 4A module diagram of a list data processing system provided by an exemplary embodiment of the present disclosure is shown, wherein the system 100 includes: a data acquisition module 101, a list construction module 102, an asynchronous insertion module 103, and a rendering module 104;
[0109] The data acquisition module 101 is used to acquire basic element information and inserted element information of the list data in response to a request to load the list data;
[0110] Wherein, the insertion element information includes insertion position parameters;
[0111] The list construction module 102 is used to construct a module sequence of the list data based on the basic element information;
[0112] The asynchronous insertion module 103 is configured to construct an asynchronous placeholder component based on the insertion element information, and list the asynchronous placeholder component in the module sequence using the insertion position parameter;
[0113] The rendering module 104 is configured to render the module sequence.
[0114] As an implementable manner, the rendering module 104 includes a loading status acquisition unit and a dynamic rendering unit;
[0115] A loading status acquisition unit, used to acquire the loading status of each module in the module sequence in real time;
[0116] The dynamic rendering unit is used to dynamically render the module sequence based on the mapping relationship between the loading status corresponding to each module and the corresponding module.
[0117] As an implementable manner, the dynamic rendering unit is further configured to render the corresponding module using a rendering skeleton screen in response to the loading state of the module being characterized as an initialization state; and / or,
[0118] The dynamic rendering unit is further configured to perform ceiling rendering on the module in response to the loading state of the module being characterized as a loading state and the module being located at the top of the viewport; and / or,
[0119] The dynamic rendering unit is further configured to render the list data in response to the module loading status being characterized as a loading success status; and / or,
[0120] The dynamic rendering unit is further configured to display a corresponding empty state prompt in response to the loading state of the module being characterized as the interface returning a no-data state.
[0121] As an implementable manner, the insertion element information further includes a list matching parameter corresponding to the insertion position parameter. The asynchronous insertion module 103 includes a list type identification unit, a parameter matching unit, and a position determination unit:
[0122] a list type identification unit, configured to identify the type of the list data;
[0123] a parameter matching unit, configured to determine the list matching parameter based on the type of the list data;
[0124] A position determining unit is configured to obtain the insertion position parameter corresponding to the list matching parameter.
[0125] As an implementable manner, the inserted element information includes map information, the basic element information includes a fixed header, and the asynchronous inserting module 103 further includes a structure determination unit and a sequence processing unit;
[0126] The structure determination unit is configured to split the fixed header into tabs and filters in response to the type of the list data being the first map scene;
[0127] The sequence processing unit is used to construct a first asynchronous placeholder component based on the map information, and insert the first asynchronous placeholder component between the tab and the filter;
[0128] The structure determination unit is further configured to write a map display / hidden flag into the additional configuration of the fixed page header in response to the type of the list data being the second map scene;
[0129] The sequence processing unit is further configured to construct a second asynchronous placeholder component using the map information, and insert the second asynchronous placeholder component below the fixed header;
[0130] Displaying the second asynchronous placeholder component based on the map visibility flag;
[0131] The display range of the first asynchronous placeholder component is larger than that of the second asynchronous placeholder component.
[0132] As an implementable manner, the inserted element information also includes hotel recommendation information, and the basic element information includes a fixed header and a header notification component:
[0133] The structure determination unit is further configured to, in response to the type of the list data being a hotel external investment scenario, split the fixed header into tabs and filters;
[0134] The sequence processing unit is further configured to construct a third asynchronous placeholder component using the hotel recommendation information, and to arrange the tab, the page header notification component, the third asynchronous placeholder component, and the filter in sequence.
[0135] Since the system embodiments generally correspond to the method embodiments, reference will be made to the description of the method embodiments for relevant details. The system embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components of the units may or may not be physical units, i.e., they may be located in one place or distributed across multiple network units. Some or all of the modules may be selected based on actual needs to achieve the objectives of the disclosed solution.
[0136] The list data processing system provided in this embodiment dynamically obtains module configuration information through an asynchronous interface based on scenario requirements, flexibly inserting or hiding components, and asynchronously loading key modules to ensure that core functions are displayed first, avoiding blocking the first screen rendering due to complex content, while ensuring functional consistency in different scenarios. Specific modules are loaded only when necessary, reducing redundant requests and rendering overhead. Incorporating lazy loading technology, non-visible areas in long lists are loaded lazily, reducing memory usage and data consumption.
[0137] Example 3
[0138] Figure 5 This is a structural diagram of an electronic device showing an example embodiment of the present disclosure. The electronic device includes a memory, a processor, and a computer program stored in the memory and used to run on the processor. When the processor executes the computer program, it implements the method for processing list data described in any of the above embodiments. Figure 5 The electronic device 90 shown is only an example and should not limit the functionality and scope of use of the embodiments of the present disclosure.
[0139] like Figure 5 As shown, the electronic device 90 may be a general-purpose computing device, such as a server device. Components of the electronic device 90 may include, but are not limited to, the at least one processor 91, the at least one memory 92, and a bus 93 connecting different system components (including the memory 92 and the processor 91).
[0140] The bus 93 includes a data bus, an address bus, and a control bus.
[0141] The memory 92 may include a volatile memory, such as a random access memory (RAM) 921 and / or a cache memory 922 , and may further include a read-only memory (ROM) 923 .
[0142] The memory 92 may also include a program tool 925 (or utility) having a set (at least one) of program modules, such program modules 924 including but not limited to: an operating system, one or more application programs, other program modules and program data, each of which or some combination may include an implementation of a network environment.
[0143] The processor 91 executes various functional applications and data processing by running the computer programs stored in the memory 92, such as the method for processing list data provided in any of the above embodiments.
[0144] The electronic device 90 can also communicate with one or more external devices 94 (e.g., a keyboard, pointing device, etc.). This communication can occur via an input / output (I / O) interface 95. Furthermore, the electronic device 90 can communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) via a network adapter 96. As shown, the network adapter 96 communicates with other modules of the electronic device 90 via a bus 93. It should be understood that, although not shown in the figure, other hardware and / or software modules can be used in conjunction with the electronic device 90, including but not limited to microcode, device drivers, redundant processors, external disk drive arrays, RAID (RAID) systems, tape drives, and data backup storage systems.
[0145] It should be noted that although several units / modules or sub-units / modules of the electronic device are mentioned in the detailed description above, this division is merely exemplary and not mandatory. In fact, according to the embodiments of the present disclosure, the features and functions of two or more units / modules described above can be embodied in one unit / module. Conversely, the features and functions of one unit / module described above can be further divided and embodied by multiple units / modules.
[0146] Example 4
[0147] An embodiment of the present disclosure further provides a computer-readable storage medium having a computer program stored thereon. When the program is executed by a processor, the method for processing list data provided in any of the above embodiments is implemented.
[0148] The readable storage medium may include, but is not limited to, a portable disk, a hard disk, a random access memory, a read-only memory, an erasable programmable read-only memory, an optical storage device, a magnetic storage device, or any suitable combination thereof.
[0149] Example 5
[0150] An embodiment of the present disclosure further provides a computer program product, including a computer program, which implements any of the above-mentioned methods for processing list data when executed by a processor.
[0151] The program code for executing the computer program product of the present disclosure may be written in any combination of one or more programming languages, and the program code may be executed entirely on the user device, partially on the user device, as a standalone software package, partially on the user device and partially on a remote device, or entirely on the remote device.
[0152] While specific embodiments of the present disclosure have been described above, those skilled in the art will appreciate that these are merely illustrative and that the scope of protection of the present disclosure is defined by the appended claims. Those skilled in the art may make various changes or modifications to these embodiments without departing from the principles and essence of the present disclosure, and such changes and modifications are intended to fall within the scope of protection of the present disclosure.
Claims
1. A method for processing list data, characterized in that: The processing method comprises: In response to a request to load list data, acquiring basic element information and inserted element information of the list data; Wherein, the insertion element information includes insertion position parameters; Constructing a module sequence of the list data based on the basic element information; Constructing an asynchronous placeholder component based on the insertion element information, and listing the asynchronous placeholder component in the module sequence using the insertion position parameter; Renders the module sequence.
2. The method for processing list data according to claim 1, wherein: The step of rendering the module sequence comprises: Obtaining the loading status of each module in the module sequence in real time; Based on the mapping relationship between the loading status corresponding to each module and the corresponding module, the module sequence is dynamically rendered.
3. The method for processing list data according to claim 2, wherein: The step of dynamically rendering the module sequence based on the mapping relationship between the loading status corresponding to each module and the corresponding module includes: In response to the loading state of the module being characterized as an initialization state, rendering the corresponding module using a rendering skeleton screen; and / or, In response to the loading state of the module being characterized as a loading state and the position of the module being at the top of the viewport, performing ceiling rendering on the module; and / or, In response to the module loading status being characterized as a loading success status, rendering the list data; and / or, In response to the loading status of the module being characterized as the interface returning a no-data state, a corresponding empty state prompt is displayed.
4. The method for processing list data according to claim 1, wherein: The insertion element information further includes a list matching parameter corresponding to the insertion position parameter, and the step of constructing an asynchronous placeholder component based on the insertion element information includes: Identifying the type of the list data; determining the list matching parameter based on the type of the list data; The insertion position parameter corresponding to the list matching parameter is obtained.
5. The method for processing list data according to claim 4, characterized in that: The insert element information includes map information, the basic element information includes a fixed page header, and the step of listing the asynchronous placeholder component in the module sequence according to the insert position parameter includes: In response to the type of the list data being the first map scene, splitting the fixed header into tabs and filters; Constructing a first asynchronous placeholder component using the map information, and inserting the first asynchronous placeholder component between the tab and the filter; In response to the type of the list data being the second map scene, writing a map display / hidden flag into the additional configuration of the fixed page header; Constructing a second asynchronous placeholder component using the map information, and inserting the second asynchronous placeholder component below the fixed header; Displaying the second asynchronous placeholder component based on the map visibility flag; The display range of the first asynchronous placeholder component is larger than that of the second asynchronous placeholder component.
6. The method for processing list data according to claim 4, characterized in that: The inserted element information further includes hotel recommendation information, the basic element information includes a fixed header and a header notification component, and the step of listing the asynchronous placeholder component in the module sequence using the insertion position parameter includes: In response to the type of the list data being a hotel external projection scenario, splitting the fixed header into tabs and filters; A third asynchronous placeholder component is constructed using the hotel recommendation information, and the tab, the page header notification component, the third asynchronous placeholder component, and the filter are arranged in sequence.
7. A system for processing list data, characterized in that: The processing system includes a data acquisition module, a list construction module, an asynchronous insertion module and a rendering module; The data acquisition module is configured to acquire basic element information and inserted element information of the list data in response to a request to load the list data; Wherein, the insertion element information includes insertion position parameters; The list construction module is used to construct a module sequence of the list data based on the basic element information; The asynchronous insertion module is configured to construct an asynchronous placeholder component based on the insertion element information, and list the asynchronous placeholder component in the module sequence using the insertion position parameter; The rendering module is used to render the module sequence.
8. An electronic device comprising a memory, a processor, and a computer program stored in the memory and configured to run on the processor, wherein: When the processor executes the computer program, the method for processing list data according to any one of claims 1 to 6 is implemented.
9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method for processing list data according to any one of claims 1 to 6 is implemented.
10. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the method for processing list data according to any one of claims 1 to 6 is implemented.