CN118972383A - A method, system, device and medium for extending an attachment upload component - Google Patents

Abstract

The invention relates to the technical field of software and discloses an extension method, a system, equipment and a medium of an accessory uploading component. The method comprises the following steps: in response to detecting an editing event in the accessory uploading component, identifying a target file acquisition mode corresponding to the editing event, and acquiring a target identifier corresponding to the target file acquisition mode; acquiring a file acquisition mode list of the accessory uploading component, and updating the file acquisition mode list based on the target identifier; and carrying out target function development on the accessory uploading component based on the updated file acquisition mode list to obtain the target accessory uploading component. By the scheme of the invention, the limitation of the traditional low-code platform in the aspect of function expansion is solved, and support is provided for expanding the file acquisition mode of the accessory uploading component.

Description

A method, system, device and medium for extending an attachment upload component

Technical Field

The present invention relates to the field of software technology, and in particular to an extension method, system, device and medium for an attachment upload component.

Background Art

As an innovative software development tool, the low-code development platform is gradually changing the traditional model of software development. Its core lies in greatly simplifying the application development process through a highly visual design interface and a series of modular building components, making the entire development process more intuitive and efficient. In addition, the low-code platform can output complete application solutions, which can cover diversified application scenarios from PC web pages to mobile pages and even WeChat applets, effectively assisting the development of mobile H5 (HyperText Markup Language 5) applications. Although the low-code development platform performs well in simplifying the construction process of mobile H5 applications, it has obvious deficiencies in scalability. For some companies with exclusive mobile native platforms, since most of the current low-code platforms do not provide the ability to integrate with external platforms, when companies try to integrate H5 applications into their own exclusive mobile native platforms, they face the dilemma of not being able to directly call the capabilities of the native platform. As attachment uploading is a basic and critical capability in mobile applications, most low-code platforms are equipped with rich attachment upload components. However, due to the limitations of low-code platforms in cross-platform integration and functional extension, it is impossible to support customized extensions of file acquisition methods in attachment upload components for specific scenarios or customer personalized needs.

Therefore, the present invention proposes an extension method, system, device and medium for an attachment upload component to solve the above-mentioned defects.

Summary of the invention

In view of this, the present invention proposes an extension method, system, device and medium for an attachment upload component, which solves the limitations of traditional low-code platforms in functional expansion and provides support for the attachment upload component to expand its file acquisition method.

Based on the above purpose, an embodiment of the present invention provides an extension method of an attachment upload component, which specifically includes the following steps:

In response to detecting an editing event in the attachment upload component, identifying a target file acquisition method corresponding to the editing event, and acquiring a target identifier corresponding to the target file acquisition method;

Obtain a file acquisition method list of the attachment upload component, and update the file acquisition method list based on the target identifier;

The target function of the attachment upload component is developed based on the updated file acquisition method list to obtain a target attachment upload component.

In some implementations, the step of updating the file acquisition method list based on the target identifier includes:

Obtain a first callback method and a first field corresponding to the target file acquisition method;

Determine whether there is an initial file acquisition method corresponding to the target identifier in the file acquisition method list;

In response to the existence of an initial file acquisition method corresponding to the target identifier in the file acquisition method list, acquiring an initial callback method and an initial field corresponding to the initial file acquisition method;

Merging the initial callback method and the first callback method according to a preset condition to obtain a target callback method;

In the file acquisition method list, the initial callback method is updated to the target callback method, and the initial field is updated to the first field.

In some implementations, the method for extending the attachment upload component further includes:

In response to the absence of a file acquisition method corresponding to the target identifier in the file acquisition method list, the target identifier, the first callback method and the first field are added to the file acquisition method list to update the file acquisition method list.

In some implementations, the step of identifying the target file acquisition method corresponding to the editing event and acquiring the target identifier corresponding to the target file acquisition method includes:

Obtaining an extension script of the attachment upload component;

Compare the file acquisition method list with the extended script, and determine whether a new file identifier exists in the extended script according to the comparison result;

In response to the presence of a newly added file identifier in the extended script, a first file acquisition method corresponding to the newly added file identifier is used as the target file acquisition method, and the newly added file identifier is used as the target identifier.

In some implementations, the method for extending the attachment upload component further includes:

In response to the absence of a newly added file identifier in the extended script, determining to update the file configuration according to the comparison result;

The file identifier corresponding to the update file configuration is obtained as the target identifier, and the second file acquisition method corresponding to the update file configuration is used as the target file acquisition method.

In some implementations, the method for extending the attachment upload component further includes:

In response to the target interface receiving the target array input by the user, mounting the target array to a preset object;

In response to the extended script of the attachment upload component accessing the preset object, triggering the editing event;

The target array includes a file identifier, a file name, a display identifier, a prompt text and/or a callback method.

In some implementations, the step of developing a target function for the attachment upload component based on the updated file acquisition method list to obtain a target attachment upload component includes:

Passing the updated file acquisition method list to the attachment upload component through dependency injection;

The attachment upload component configures the corresponding target function according to each file acquisition method included in the updated file acquisition method list, and uses the attachment upload component configured with all the target functions as the target attachment upload component.

Another aspect of the embodiment of the present invention further provides an extension system for an attachment upload component, including:

an identification unit configured to, in response to detecting an editing event in the attachment upload component, identify a target file acquisition method corresponding to the editing event, and acquire a target identifier corresponding to the target file acquisition method;

An updating unit configured to obtain a file acquisition method list of the attachment upload component and update the file acquisition method list based on the target identifier;

The extension unit is configured to develop a target function for the attachment upload component based on the updated file acquisition method list to obtain a target attachment upload component.

According to another aspect of an embodiment of the present invention, a computer device is provided, comprising: at least one processor; and a memory, wherein the memory stores a computer program executable on the processor, and the computer program implements the steps of the above method when executed by the processor.

According to another aspect of the embodiments of the present invention, a computer-readable storage medium is provided, which stores a computer program that implements the above method steps when executed by a processor.

The present invention has at least the following beneficial technical effects: the extension method of the attachment upload component of the present invention, by setting a file acquisition method list, allows the user to update the file acquisition method list through customized editing events of the file acquisition method to manage the functions of the attachment upload component, thereby providing more functions for the attachment upload component in the low-code platform to meet the increasingly complex business needs of users, solving the limitations of traditional low-code platforms in functional expansion, and providing support for the attachment upload component to expand its file acquisition method.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present invention. For ordinary technicians in this field, other embodiments can be obtained based on these drawings without paying creative work.

FIG1 is a block diagram of an embodiment of a method for extending an attachment upload component provided by the present invention;

FIG. 2 is a schematic diagram of an embodiment of an execution process of an extension method for an attachment upload component provided by the present invention;

FIG3 is a schematic diagram of an embodiment of an extension system for an attachment upload component provided by the present invention;

FIG4 is a schematic diagram of the structure of a computer device according to an embodiment of the present invention;

FIG5 is a schematic diagram of the structure of an embodiment of a computer-readable storage medium provided by the present invention.

DETAILED DESCRIPTION

In order to make the objectives, technical solutions and advantages of the present invention more clearly understood, the embodiments of the present invention are further described in detail below in combination with specific embodiments and with reference to the accompanying drawings.

It should be noted that all expressions using "first" and "second" in the embodiments of the present invention are for distinguishing two non-identical entities with the same name or non-identical parameters. It can be seen that "first" and "second" are only for the convenience of expression and should not be understood as limitations on the embodiments of the present invention. The subsequent embodiments will not explain this one by one.

With the assistance of low-code development platforms, the development process of mobile H5 applications is particularly convenient. Users can use rich component libraries and intuitive drag-and-drop editors to design mobile applications that meet business needs and have good user experience without deep programming knowledge. Attachment upload is a basic and key capability in mobile forms, and most low-code platforms are equipped with rich attachment upload components. On the mobile side, users can obtain and upload attachments in a variety of ways, including but not limited to selecting from the album, taking photos, accessing local files on the phone, and shooting short videos. However, since the H5 application page itself does not have the authority to call the native system capabilities, in order to realize these rich file acquisition methods, the interaction between the mobile H5 application and the native system usually needs to rely on specific "bridge" technology, such as Hybrid technology. Hybrid technology is a development method that combines native system and H5 application technology. It allows users to use native API (Application Programming Interface) and Web (World Wide Web) technology in one application at the same time. The advantage is that it can maintain the flexibility and cross-platform capabilities of Web technology while also using native API to improve application performance and user experience. Since existing low-code platforms often do not provide the ability to integrate with external platforms, enterprises or users face the dilemma of being unable to call on native platform capabilities when trying to integrate H5 pages into exclusive mobile native platforms. Current low-code platforms usually only provide fixed built-in file acquisition methods for uploading attachments. For example, the "Picture Upload" component in the low-code platform may only support the two methods of "Select from Album" and "Take a Photo". When customers need to add more personalized or special file acquisition methods, such as "Scan from Scanner", the low-code platform cannot meet such customization requirements due to its lack of scalability. In addition, the attachment upload component fixed in the low-code platform cannot be easily adapted to various mobile native platforms. This limitation has undoubtedly caused some trouble for those enterprises or institutions that have exclusive mobile native platforms.

In order to solve the above defects, the first aspect of the embodiment of the present invention proposes an extension method of the attachment upload component. As shown in FIG1 , the method comprises the following steps:

Step S100, in response to detecting an editing event in the attachment upload component, identifying a target file acquisition method corresponding to the editing event, and acquiring a target identifier corresponding to the target file acquisition method;

Step S200, obtaining a file acquisition method list of the attachment upload component, and updating the file acquisition method list based on the target identifier;

Step S300: Develop the target function of the attachment upload component based on the updated file acquisition method list to obtain the target attachment upload component.

In some embodiments, unlike the attachment upload component inherent in the existing low-code development platform on the market, the present invention adds a "file acquisition method" property in the property panel of the attachment upload component to customize the file acquisition method list according to the user's needs. The file acquisition method list is a file acquisition method selection list that pops up from the page in the form of a pop-up layer when the user clicks the upload button of the attachment upload component. The items in the list may include "select from the album", "take a photo", "shoot a short video" and/or "mobile phone local file" and other file acquisition method options.

In some embodiments, a read-only text box will be used to display the name of the file acquisition method configured by the current attachment upload component at a preset position of the "File Acquisition Method" property panel of the low-code development platform. If there are multiple file acquisition methods, the names are separated by commas. An edit button corresponding to the text box is set on the property panel. By clicking the edit button, the low-code development platform will pop up a pop-up box titled "File Acquisition Method Editor". The pop-up box can display the currently enabled file acquisition methods through a list. The pop-up box list provides "Add", "Delete", "Move Up", "Move Down", and "Extend" buttons above. The user selects an existing file acquisition method entry in the above pop-up box list, and then clicks the "Move Up" or "Move Down" button to change the display position of the file acquisition method option. The user selects an existing file acquisition method entry in the pop-up box list, and then clicks the "Delete" button to remove the file acquisition method from the removal pop-up box list. The user can customize the file acquisition method option in the attachment upload component by editing the "File Acquisition Method" property. Figure 2 is a schematic diagram of an embodiment of the execution process of the extension method of the attachment upload component provided by the present invention. If the user thinks that the file acquisition method in the current pop-up list is not enough to cope with the actual business scenario, the user can customize the file acquisition method by clicking the "Add" button. After clicking the "Add" button, the low-code development platform will pop up a drop-down box, which displays all the built-in file acquisition methods of the current low-code platform, as well as the custom file acquisition methods added by the user by writing js (JavaScript, a just-in-time compiled programming language) plug-in code. The user clicks on any file acquisition method entry to add the file acquisition method to the pop-up list. If the user wants to add a custom file acquisition method, or wants to adapt a built-in file acquisition method to multiple platforms, click the "Extend" button, and the low-code platform will switch the list displayed in the current pop-up box to a code editor for writing js extension plug-ins, hereinafter referred to as js extension scripts. Editing events refer to events that change the file acquisition method in the file acquisition method list. The file acquisition method changed in the editing event is used as the target file acquisition method, and the changed content is synchronously updated to the file acquisition method list.

In some implementations, every time a user writes and saves the js extension script or opens the "File Acquisition Method Editor" for the first time, the low-code platform needs to re-read and parse the content of the js extension script, identify the custom file acquisition method added by the user, and synchronously update it to the file acquisition method list. After the user completes editing the mobile form, saves and generates the entire application, the low-code platform will generate the code for the mobile H5 application based on the metadata. In the entry file index.html, the js extension script will be referenced as a script tag, or the task of loading the js extension script will be handed over to the mobile framework script to execute, thereby realizing the on-demand introduction of file acquisition methods and generating the final attachment upload component.

The extension method of the attachment upload component of the present invention, by setting a file acquisition method list, allows the user to update the file acquisition method list through customized editing events of the file acquisition method to manage the functions of the attachment upload component, thereby providing more functions for the attachment upload component in the low-code platform to meet the increasingly complex business needs of users, solving the limitations of traditional low-code platforms in functional expansion, and providing support for the attachment upload component to expand its file acquisition method.

In some embodiments, the extension method of the attachment upload component of the present invention also includes: in response to the target interface receiving a target array input by the user, mounting the target array to a preset object; in response to the extension script of the attachment upload component accessing the preset object, triggering an editing event; wherein the target array includes a file identifier, a file name, a display identifier, a prompt text and/or a callback method.

In some embodiments, the js extension script corresponds to a js file in the mobile terminal running framework, which is globally unique. When the mobile terminal H5 application is actually running, the js extension script will be loaded first, so the code written by the user in the js extension script will take effect in all attachment upload components in all mobile terminal H5 applications. In addition, it should be noted that since the js extension script is globally unique, it is necessary to avoid the problem of mutual coverage caused by two users editing the js extension script at the same time, so it can be ensured that only one user can edit the js extension script at the same time by locking. When the user writes the js extension script, it is necessary to return all the information of the custom file acquisition method or the number value and extension method of the built-in file acquisition method according to the specified format. Whether the file acquisition method is adapted to multiple platforms or a custom file acquisition method is added, the data structure of the target array is the same. The difference is that when writing a custom file acquisition method, all necessary configurations need to be given, and when adapting the file acquisition method to multiple platforms, only a file identifier pointing to the built-in file acquisition method and a callback method for extension are needed. Other configurations, such as configurations such as file names, can reuse the file name of the built-in file acquisition method by default without change. All configurations required for the file acquisition method are shown in Table 1 below.

Table 1

The extension method of the attachment upload component of the present invention can flexibly support the extension of built-in or customized file acquisition methods in the file acquisition method list through the target array, which can simplify the multi-platform expansion work of the component and improve the scalability of the low-code platform.

In some embodiments, based on the target identifier, the step of updating the file acquisition method list includes: obtaining a first callback method and a first field corresponding to the target file acquisition method; determining whether there is an initial file acquisition method corresponding to the target identifier in the file acquisition method list; in response to the existence of an initial file acquisition method corresponding to the target identifier in the file acquisition method list, obtaining an initial callback method and an initial field corresponding to the initial file acquisition method; merging the initial callback method and the first callback method according to preset conditions to obtain a target callback method; updating the initial callback method to the target callback method in the file acquisition method list, and updating the initial field to the first field.

In some embodiments, the extension method of the attachment upload component of the present invention also includes: in response to the absence of a file acquisition method corresponding to the target identifier in the file acquisition method list, adding the target identifier, the first callback method and the first field to the file acquisition method list to update the file acquisition method list.

In some implementations, the js extension script only needs to obtain the FilePickerOption array (i.e., the target array) edited by the user to extend the user-defined file acquisition method in the attachment upload component. The FilePickerOption array is an interface definition for the js extension script to accept the configuration information of the file acquisition method, and can return all the information of the file acquisition method in the specified format to the js extension script. There is no limit to the specific way in which the js extension script obtains the FilePickerOption array. For example, the user can be required to mount the FilePickerOption array to a certain attribute of the window object. Since the window object is globally accessible, it is only necessary to ensure that the js extension script is loaded when the mobile form is running. The mobile terminal framework script can read the window object and obtain the configuration information of the user-configured custom file acquisition method according to the FilePickerOption array. In addition, the loading method of the js extension script is also not limited. When generating the code, a script tag can be directly generated in the entry file index.html of the H5 application page, and the js extension script can be directly loaded when the H5 application page is loaded. The js extension script can also be dynamically loaded when the mobile form is running. In the mobile framework script, when a built-in file acquisition method needs to be added to the file acquisition method list, all information about the file acquisition method in the specified format is also returned to the js extension script through the FilePickerOption array.

In some embodiments, when the file acquisition method list already has a built-in file acquisition method (i.e., the initial file acquisition method) corresponding to the file identifier (i.e., the target identifier) of the custom file acquisition method (i.e., the target file acquisition method), and the attachment upload component should not care about the merging of the file acquisition method list when the mobile form is running, the mobile terminal framework merges the file acquisition methods with the same file identifier when the mobile form is running. That is, after the js extension script is loaded, the mobile terminal framework script will read the configuration information of the file acquisition method customized by the developer, and merge the custom file acquisition method and the built-in file acquisition method with the same file identifier according to the corresponding relationship of the file identifier. The above-mentioned merger refers to packaging and merging the callback method (first callback method) of the custom file acquisition method and the callback method (initial callback method) of the built-in file acquisition method, and the other fields are all overwritten with the built-in configuration information with the custom configuration information, that is, the initial field is overwritten with the first field. When the file acquisition method list does not have a built-in file acquisition method corresponding to the file identifier of the custom file acquisition method, the custom file acquisition method is directly added to the file acquisition method list. The built-in file acquisition method is the file acquisition method implemented by default in the mobile terminal framework. The first field and the initial field include the file name, prompt text, option visibility flag and/or international configuration of the file name in Table 1. Since the callback method is a function and may contain complex logic, they cannot be directly merged by simple value overwriting. It is necessary to create a new callback (i.e., the target callback method) to wrap and merge the first callback method and the initial callback method. The target callback calls the first callback method and the initial callback method in some way (such as sequential call) internally. When a file acquisition request occurs, the first callback method is called first. If the return value of the first callback method is empty, the initial callback method is called.

The extension method of the attachment upload component of the present invention provides a flexible way to adjust the priority and behavior between built-in and custom functions, and realizes a powerful and flexible attachment upload component. The attachment upload component not only supports multi-platform and multi-terminal adaptation, but also allows users to expand the file acquisition method according to needs.

In some embodiments, the steps of identifying a target file acquisition method corresponding to an editing event and acquiring a target identifier corresponding to the target file acquisition method include: acquiring an extended script of an attachment upload component; comparing a file acquisition method list and an extended script, and determining whether the extended script has a new file identifier based on the comparison result; in response to the existence of a new file identifier in the extended script, using a first file acquisition method corresponding to the new file identifier as a target file acquisition method, and using the new file identifier as a target identifier.

In some embodiments, the extension method of the attachment upload component of the present invention also includes: in response to the absence of a new file identifier in the extension script, determining an updated file configuration based on a comparison result; obtaining a file identifier corresponding to the updated file configuration as a target identifier, and using a second file acquisition method corresponding to the updated file configuration as a target file acquisition method.

The extension method of the attachment upload component of the present invention can not only expand the custom file acquisition method in the attachment upload component, but also modify the built-in file acquisition method of the low-code platform as needed and expand it to the attachment upload component, bringing unprecedented convenience and efficiency to the development of mobile H5 applications, improving development speed and flexibility, and enabling more companies and individuals to easily integrate H5 pages into their exclusive mobile native platforms.

In some embodiments, the target function of the attachment upload component is developed based on the updated file acquisition method list to obtain the step of the target attachment upload component, including: passing the updated file acquisition method list to the attachment upload component through dependency injection; the attachment upload component configures the corresponding target function according to each file acquisition method included in the updated file acquisition method list, and uses the attachment upload component configured with all target functions as the target attachment upload component. Among them, the target attachment upload component can have all target functions, but each target function can determine whether it is available in the current application platform according to the option visible mark of the corresponding file acquisition method. If it is not available, the target function will not be displayed. The option visible mark is set according to user needs.

The extension method of the attachment upload component of the present invention, by setting a file acquisition method list, allows the user to update the file acquisition method list through customized editing events of the file acquisition method to manage the functions of the attachment upload component, thereby providing more functions for the attachment upload component in the low-code platform to meet the increasingly complex business needs of users, solving the limitations of traditional low-code platforms in functional expansion, and providing support for the attachment upload component to expand its file acquisition method.

Based on the same inventive concept, according to another aspect of the present invention, as shown in FIG. 3 , an embodiment of the present invention further provides an extension system for an attachment upload component, including:

The identification unit 110 is configured to, in response to detecting an editing event in the attachment upload component, identify a target file acquisition method corresponding to the editing event, and obtain a target identifier corresponding to the target file acquisition method;

The updating unit 120 is configured to obtain a file acquisition method list of the attachment upload component and update the file acquisition method list based on the target identifier;

The extension unit 130 is configured to develop a target function for the attachment upload component based on the updated file acquisition method list to obtain a target attachment upload component.

The extension system of the attachment upload component of the present invention, by setting a file acquisition method list, allows the user to update the file acquisition method list through customized editing events of the file acquisition method to manage the functions of the attachment upload component, thereby providing more functions for the attachment upload component in the low-code platform to meet the increasingly complex business needs of users, solving the limitations of traditional low-code platforms in functional expansion, and providing support for the attachment upload component to expand its file acquisition method.

Based on the same inventive concept, according to another aspect of the present invention, as shown in FIG. 4 , an embodiment of the present invention further provides a computer device 30, which includes a processor 310 and a memory 320, wherein the memory 320 stores a computer program 321 that can be run on the processor, and the processor 310 executes the steps of the above method when executing the program.

Based on the same inventive concept, according to another aspect of the present invention, as shown in FIG. 5 , an embodiment of the present invention further provides a computer-readable storage medium 40 , which stores a computer program 410 that performs the above method when executed by a processor.

Finally, it should be noted that a person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program, and the program can be stored in a computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, the storage medium of the program can be a disk, an optical disk, a read-only storage memory (ROM) or a random access memory (RAM), etc. The above-mentioned computer program embodiments can achieve the same or similar effects as the corresponding above-mentioned any method embodiments.

It will also be appreciated by those skilled in the art that various exemplary logic blocks, modules, circuits and algorithm steps described in conjunction with the disclosure herein can be implemented as electronic hardware, computer software or a combination of the two. In order to clearly illustrate this interchangeability of hardware and software, a general description has been given to the functions of various schematic components, blocks, modules, circuits and steps. Whether this function is implemented as software or hardware depends on specific applications and the design constraints imposed on the entire system. Those skilled in the art can implement the function in various ways for each specific application, but this implementation decision should not be interpreted as causing a departure from the disclosed scope of the embodiments of the present invention.

The above are exemplary embodiments disclosed in the present invention, but it should be noted that various changes and modifications may be made without departing from the scope of the embodiments disclosed in the present invention as defined in the claims. The functions, steps and/or actions of the method claims according to the disclosed embodiments described herein do not need to be performed in any particular order. The serial numbers of the embodiments disclosed in the above embodiments of the present invention are for description only and do not represent the advantages and disadvantages of the embodiments. In addition, although the elements disclosed in the embodiments of the present invention may be described or required in individual form, they may also be understood as multiple unless explicitly limited to the singular.

It should be understood that, as used herein, the singular forms "a", "an" are intended to include the plural forms as well, unless the context clearly supports an exception. It should also be understood that, as used herein, "and/or" refers to any and all possible combinations including one or more of the associated listed items.

A person skilled in the art should understand that the discussion of any of the above embodiments is only exemplary and is not intended to imply that the scope of the disclosure of the embodiments of the present invention (including the claims) is limited to these examples; under the concept of the embodiments of the present invention, the technical features in the above embodiments or different embodiments can also be combined, and there are many other changes in different aspects of the above embodiments of the present invention, which are not provided in detail for the sake of simplicity. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the embodiments of the present invention should be included in the protection scope of the embodiments of the present invention.

Claims (10)

1. A method for extending an attachment upload component, comprising: In response to detecting an editing event in the attachment upload component, identifying a target file acquisition method corresponding to the editing event, and acquiring a target identifier corresponding to the target file acquisition method; Obtain a file acquisition method list of the attachment upload component, and update the file acquisition method list based on the target identifier; The target function of the attachment upload component is developed based on the updated file acquisition method list to obtain a target attachment upload component. 2. The method for extending the attachment upload component according to claim 1, wherein the step of updating the file acquisition method list based on the target identifier comprises: Obtain a first callback method and a first field corresponding to the target file acquisition method; Determine whether there is an initial file acquisition method corresponding to the target identifier in the file acquisition method list; In response to the existence of an initial file acquisition method corresponding to the target identifier in the file acquisition method list, acquiring an initial callback method and an initial field corresponding to the initial file acquisition method; Merging the initial callback method and the first callback method according to a preset condition to obtain a target callback method; In the file acquisition method list, the initial callback method is updated to the target callback method, and the initial field is updated to the first field. 3. The method for extending the attachment upload component according to claim 2, further comprising: In response to the absence of a file acquisition method corresponding to the target identifier in the file acquisition method list, the target identifier, the first callback method and the first field are added to the file acquisition method list to update the file acquisition method list. 4. The method for extending the attachment upload component according to claim 1, wherein the step of identifying the target file acquisition method corresponding to the editing event and acquiring the target identifier corresponding to the target file acquisition method comprises: Obtaining an extension script of the attachment upload component; Compare the file acquisition method list with the extended script, and determine whether a new file identifier exists in the extended script according to the comparison result; In response to the presence of a new file identifier in the extended script, a first file acquisition method corresponding to the new file identifier is used as the target file acquisition method, and the new file identifier is used as the target identifier. 5. The method for extending the attachment upload component according to claim 4, further comprising: In response to the absence of a newly added file identifier in the extended script, determining to update the file configuration according to the comparison result; The file identifier corresponding to the update file configuration is obtained as the target identifier, and the second file acquisition method corresponding to the update file configuration is obtained as the target file acquisition method. 6. The method for extending the attachment upload component according to claim 1, further comprising: In response to the target interface receiving the target array input by the user, mounting the target array to a preset object; In response to the extended script of the attachment upload component accessing the preset object, triggering the editing event; The target array includes a file identifier, a file name, a display identifier, a prompt text and/or a callback method. 7. The method for extending the attachment upload component according to claim 1, wherein the step of developing a target function of the attachment upload component based on the updated file acquisition method list to obtain a target attachment upload component comprises: Passing the updated file acquisition method list to the attachment upload component through dependency injection; The attachment upload component configures the corresponding target function according to each file acquisition method included in the updated file acquisition method list, and uses the attachment upload component configured with all the target functions as the target attachment upload component. 8. An extension system for an attachment upload component, comprising: an identification unit configured to, in response to detecting an editing event in the attachment upload component, identify a target file acquisition method corresponding to the editing event, and acquire a target identifier corresponding to the target file acquisition method; An updating unit configured to obtain a file acquisition method list of the attachment upload component and update the file acquisition method list based on the target identifier; The extension unit is configured to develop a target function for the attachment upload component based on the updated file acquisition method list to obtain a target attachment upload component. 9. A computer device comprising: at least one processor; and A memory storing a computer program executable on the processor, wherein the processor executes the steps of the method according to any one of claims 1 to 7 when executing the program. 10. A computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, performs the steps of the method according to any one of claims 1 to 7.