CN115454537A

CN115454537A - Plug-in management method and device, electronic equipment and computer readable storage medium

Info

Publication number: CN115454537A
Application number: CN202211248622.7A
Authority: CN
Inventors: 罗湘连
Original assignee: Ping An Bank Co Ltd
Current assignee: Ping An Bank Co Ltd
Priority date: 2022-10-12
Filing date: 2022-10-12
Publication date: 2022-12-09

Abstract

The application provides a plug-in management method, a plug-in management device, an electronic device and a computer readable storage medium. The method is applicable to a code editor, after obtaining the name of a plug-in to be managed in a plug-in list to be managed, combining the read default plug-in list configuration and actual plug-in list configuration of the plug-in list to be managed to obtain a fused plug-in list configuration, splicing a target download link of the plug-in to be managed according to ideal plug-in version information of the fused plug-in list configuration, finally judging whether the plug-in to be managed is installed in the code editor according to the name of the plug-in, and managing the plug-in to be managed according to a judgment result and the target download link. According to the method, the batch installation of the plug-ins is realized through the plug-in list, and the version information is determined according to the configuration of the fusion plug-in list, so that the automatic update of the plug-ins is avoided, the version synchronization of the plug-ins is realized, the possibility of code conflict is reduced, and the development efficiency is improved.

Description

Plug-in management method and device, electronic equipment and computer readable storage medium

Technical Field

The present application relates to the field of software development technologies, and in particular, to a plug-in management method and apparatus, an electronic device, and a computer-readable storage medium.

Background

With the prosperous development of plug-in ecology in the code editor, the types of plug-ins used by research and development teams in software development are gradually increased.

Specifically, before software development, developers need to install plug-ins used by research and development teams one by one to ensure an environment basically consistent with team development, but the method is obviously complicated and has low development efficiency; in addition, because most plug-ins in the code editor are automatically updated by default when installed, and for some special plug-ins, a specific version sometimes needs to be appointed, and automatic updating is not needed, which inevitably causes the version of the plug-ins installed by new and old developers to be inconsistent, thereby bringing about some differences of development environments, especially for code formatting plug-ins, if the version of the plug-ins is different, different formatting is easily generated, which causes certain troubles to review and comparison of codes, and even causes code conflict.

Therefore, the current method has the technical problems of high possibility of code collision and low development efficiency, and needs to be improved.

Disclosure of Invention

The application provides a plug-in management method, a plug-in management device, an electronic device and a computer-readable storage medium, which are used for solving the technical problems of high possibility of code conflict and low development efficiency in the current method.

In order to solve the technical problem, the present application provides the following technical solutions:

the application provides a plug-in management method, which is suitable for a code editor and comprises the following steps:

acquiring the plug-in name of the plug-in to be managed in the plug-in list to be managed;

reading the default plug-in list configuration and the actual plug-in list configuration of the plug-in list to be managed;

merging the default plug-in list configuration and the actual plug-in list configuration to obtain a fused plug-in list configuration;

traversing the configuration of the fusion plug-in list, and splicing the target download link of the plug-in to be managed according to the version information of the ideal plug-in the configuration of the fusion plug-in list;

and judging whether the plug-in to be managed is installed in the code editor or not according to the plug-in name of the plug-in to be managed, and managing the plug-in to be managed according to a judgment result and the target download link.

Correspondingly, the present application further provides a plug-in management device, which is suitable for a code editor, and the device includes:

the first acquisition module is used for acquiring the plug-in name of the plug-in to be managed in the plug-in list to be managed;

the configuration reading module is used for reading the default plug-in list configuration and the actual plug-in list configuration of the plug-in list to be managed;

the configuration merging module is used for merging the default plug-in list configuration and the actual plug-in list configuration to obtain a fused plug-in list configuration;

the link splicing module is used for traversing the configuration of the fusion plug-in list and splicing the target download link of the plug-in to be managed according to the version information of the ideal plug-in the configuration of the fusion plug-in list;

and the management module is used for judging whether the plug-in to be managed is installed in the code editor according to the plug-in name of the plug-in to be managed and managing the plug-in to be managed according to the judgment result and the target download link.

Meanwhile, the application provides an electronic device, which comprises a processor and a memory, wherein the memory is used for storing a computer program, and the processor is used for operating the computer program in the memory so as to execute the steps in the plug-in management method.

In addition, the present application also provides a computer-readable storage medium, where multiple instructions are stored, and the instructions are suitable for being loaded by a processor to execute the steps in the plug-in management method.

Has the advantages that: the application provides a plug-in management method, a plug-in management device, an electronic device and a computer readable storage medium, wherein the method, the device, the electronic device and the computer readable storage medium are suitable for a code editor. Specifically, the method includes the steps of firstly obtaining a plug-in name of a plug-in to be managed in a plug-in list to be managed, then reading default plug-in list configuration and actual plug-in list configuration of the plug-in list to be managed, then combining the default plug-in list configuration and the actual plug-in list configuration to obtain fusion plug-in list configuration, then traversing the fusion plug-in list configuration, splicing a target download link of the plug-in to be managed according to ideal plug-in version information in the fusion plug-in list configuration, finally judging whether the plug-in to be managed is installed in a code editor according to the plug-in name of the plug-in to be managed, and managing the plug-in to be managed according to a judgment result and the target download link. The method realizes the batch installation of the plug-ins to be managed through the plug-in list to be managed, the target download link of the plug-ins to be managed is obtained by splicing according to the ideal plug-in version information configured by fusing the plug-in list, the automatic update of the plug-ins is avoided based on the plug-in version information, the synchronization of the plug-in versions is realized, the development environment consistent with a research and development team is ensured, the possibility of code conflict is reduced, the code review and comparison can be more concentrated on the code, and other problems caused by code formatting or environment are not needed to be analyzed, so that the development efficiency is improved.

Drawings

The technical solution and other advantages of the present application will become apparent from the detailed description of the embodiments of the present application with reference to the accompanying drawings.

Fig. 1 is a schematic view of a scenario of an application of a plug-in management method provided in an embodiment of the present application.

Fig. 2 is a main flow diagram of a plug-in management method provided in an embodiment of the present application.

Fig. 3 is a sub-flow schematic diagram of a plug-in management method provided in an embodiment of the present application.

Fig. 4 is an interface schematic diagram of a plug-in mounting interface provided in an embodiment of the present application.

Fig. 5 is a schematic structural diagram of a plug-in management device according to an embodiment of the present application.

Fig. 6 is a schematic structural diagram of an electronic device provided in an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. It is to be understood that the embodiments described are only a few embodiments of the present application and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The terms "including" and "having," and any variations thereof, in the description and claims of this application are intended to cover non-exclusive inclusions; the division of the modules presented in this application is merely a logical division, and in practical applications, there may be other divisions, for example, multiple modules may be combined or integrated into another system, or some features may be omitted, or not implemented.

The application provides a plug-in management method, a plug-in management device, an electronic device and a computer readable storage medium, wherein the plug-in management device can be integrated in the electronic device, and the electronic device can be a server or a terminal.

Referring to fig. 1, fig. 1 is a schematic view of a scenario in which the plug-in management method provided in the embodiment of the present application is applied, and as shown in fig. 1, the scenario may include terminals and devices, and the terminals, the devices, and the terminals and the devices are connected and communicated through the internet formed by various gateways. The application scenario at least comprises a background development terminal 101 and a processor 102, wherein:

the development terminal 101 refers to a terminal operated by a developer, and may be a notebook computer, a computer, or the like equipped with a code editor (e.g., vscode).

The server 102 may be an independent server, or a server network or a server cluster composed of servers; for example, the server described in the present application includes, but is not limited to, a computer, a network host, a database server, and a Cloud server formed by an application server or a plurality of servers, wherein the Cloud server is formed by a large number of computers or network servers based on Cloud Computing (Cloud Computing). The server 102 may be a server providing various services, for example, for storing information such as default plug-in list configuration, actual plug-in list configuration, and the like, for performing data analysis, and the like.

A communication link is arranged between the development terminal 101 and the server 102 to realize information interaction; the type of communication link may include a wired line, a wireless communication link, or a fiber optic cable, etc., and the application is not limited thereto.

Specifically, the development terminal obtains the plug-in name of the plug-in to be managed in the plug-in list to be managed through the code editor, reads the default plug-in list configuration and the actual plug-in list configuration of the plug-in list to be managed from the server, merges the default plug-in list configuration and the actual plug-in list configuration through the code editor to obtain a fusion plug-in list configuration, traverses the fusion plug-in list configuration, splices the target download link of the plug-in to be managed according to the ideal plug-in version information in the fusion plug-in list configuration, judges whether the plug-in to be managed is installed in the code editor or not according to the plug-in name of the plug-in to be managed, and manages the plug-in to be managed according to the judgment result and the target download link. In the whole process, developers only need to operate the code editor to execute a command, the command can install the plug-ins to be managed in the list in a batch mode by one key according to the list of the plug-ins to be managed agreed by a research and development team, meanwhile, the plug-ins can be updated automatically by default, the command also sets the required version of the plug-ins through the actual plug-in list configuration set by the developers, and therefore any developer in the research and development team can download and install the plug-ins to be managed through the command, the research and development team is enabled to maintain a consistent development environment, the possibility of code conflict is reduced, and the development efficiency is improved.

It should be noted that the scenario diagram shown in fig. 1 is only an example, and the terminal and the scenario described in the embodiment of the present application are for more clearly illustrating the technical solution of the embodiment of the present application, and do not form a limitation on the technical solution provided in the embodiment of the present application, and as a person having ordinary skill in the art knows, with the evolution of the system and the occurrence of a new service scenario, the technical solution provided in the embodiment of the present application is also applicable to similar technical problems. The following are detailed descriptions. It should be noted that the following description of the embodiments is not intended to limit the preferred order of the embodiments.

In the embodiment of the present application, please refer to fig. 2, where fig. 2 is a main flow diagram of a plug-in management method provided in the embodiment of the present application, and the plug-in management method is suitable for a code editor. The method at least comprises the following steps:

s201: and acquiring the plug-in name of the plug-in to be managed in the plug-in list to be managed.

In order to keep the development environment consistent with that of the research and development team, developers need to individually install plug-ins used by the research and development team to the code editor before writing the code. Therefore, aiming at the method of independently downloading and installing each plug-in, the embodiment of the application provides a new idea, namely, plug-ins used by a research and development team are summarized and customized into a list of the plug-ins to be managed, and developers can install the list of the plug-ins to be managed by one key, so that the code editor can automatically download and install the plug-ins to be managed in the list of the plug-ins to be managed, the time for the developers to install the plug-ins is greatly saved, and the development experience and the efficiency of the developers are improved.

The plug-in list to be managed refers to a list obtained by summarizing and sorting plug-ins used by a research and development team; the plug-in to be managed refers to one plug-in a list of plug-ins to be managed.

S202: and reading the default plug-in list configuration and the actual plug-in list configuration of the plug-in list to be managed.

After the plug-in list to be managed is obtained, the code editor can automatically read the default plug-in list configuration and the actual plug-in list configuration corresponding to the plug-in list to be managed from the server. The default plugin list configuration refers to a configuration file which is default by a system and not modified by people and contains complete configuration information of each plugin, and the configuration file mainly comprises a version configuration item of the plugin, the name of the plugin, the function of the plugin and the like; the actual plug-in list configuration refers to a configuration file which is manually set according to requirements of a research and development team and contains key configuration information of each plug-in, and the configuration file mainly comprises version configuration items of the plug-ins, names of the plug-ins and the like, wherein the version configuration items comprise ideal plug-in version information and plug-in updating configuration, the ideal plug-in version information refers to a version number set by the research and development team according to the actual development requirements, and the plug-in updating configuration refers to configuration set by the research and development team according to the actual development requirements and used for disabling the automatic plug-in updating function.

It should be noted that, in the embodiment of the present application, in order to avoid a difference in development environment due to a difference in plug-in version caused by plug-in automatic update, a general plug-in update configuration is set to disable a plug-in automatic update function.

S203: and combining the default plug-in list configuration and the actual plug-in list configuration to obtain the fusion plug-in list configuration.

Since the actual plugin list configuration is mainly a configuration file of key configuration information of each plugin set by a human according to the requirements of a research and development team, and cannot include complete configuration information of each plugin, it is necessary to merge the default plugin list configuration and the actual plugin list configuration to obtain a fused plugin list configuration.

In one embodiment, the merging process includes the following specific steps: creating an initial plug-in list configuration; comparing the default plug-in list configuration with the actual plug-in list configuration, and determining conflict configuration items and non-conflict configuration items; taking the configuration of the conflict configuration item in the actual plug-in list configuration as the target configuration of the conflict configuration item; determining the target configuration of a non-conflict configuration item according to the default plug-in list configuration and the actual plug-in list configuration; and updating the initial plug-in list configuration according to the target configuration of the conflict configuration item and the target configuration of the non-conflict configuration item to obtain the fusion plug-in list configuration. The initial plug-in list configuration refers to an empty configuration file which only comprises all the plug-ins, and configuration information of the empty configuration file needs to be filled in subsequently; conflicting configuration items refer to items in which the configuration information in the configuration item is inconsistent.

Taking the example that the plug-in list to be managed includes a, B, C and D plug-ins to be managed, the default plug-in list configuration of a includes four configuration items, namely a (including configuration 1, 2), B (including configuration 3, 4), C (including configuration 6, 7) and D (including configuration 8, 9), and the actual plug-in list configuration includes two items, namely a (including configuration 1', 2 ') and B (including configuration 3', 4', 5 '). Therefore, the conflict configuration items are determined to be a and b, the non-conflict configuration items are c and d, and the configuration of the conflict configuration items in the actual plug-in list configuration is used as the target configuration of the conflict configuration items, namely the target configuration of the conflict configuration item a is 1' and 2', and the target configuration of the conflict configuration item b is 3', 4' and 5'; according to the default plugin list configuration and the actual plugin list configuration, determining the target configuration of a non-conflict configuration item, namely the target configuration of the non-conflict configuration item is 6 and 7, and the target configuration of a non-conflict configuration item d is 8 and 9, and updating the initial plugin list configuration according to the target configuration of the conflict configuration item and the target configuration of the non-conflict configuration item, namely the configuration item of the plugin A to be managed comprises a (configuration comprising 1' and 2 '), b (configuration comprising 3', 4' and 5 '), c (configuration comprising 6 and 7) and d (configuration comprising 8 and 9), so that the initial plugin list configuration can be updated to obtain a fused plugin list configuration.

It should be noted that, for the process of merging the two configurations, the core is that if there is a conflicting configuration item, the configuration in the default plugin list configuration is directly used as the configuration of the configuration item in the fused plugin list if the configuration item in the actual plugin list configuration is null.

S204: traversing the configuration of the fusion plug-in list, and splicing the target download link of the plug-in to be managed according to the version information of the ideal plug-in the configuration of the fusion plug-in list.

In one embodiment, since the default downloading of the official is the latest version of the plug-in, but this may not be consistent with the version of the plug-in required by the research and development team, the target download link needs to be spliced according to the version of the plug-in agreed by the research and development team, and the specific steps include: acquiring a default download link of a plug-in to be managed; traversing the configuration of the fusion plug-in list, and determining the ideal plug-in version information of the plug-in to be managed from the version configuration items configured by the fusion plug-in list; and splicing to obtain the target download link of the plug-in to be managed according to the default download link and the ideal plug-in version information of the plug-in to be managed. The default download link is the link copied in the download completion item after the official default download.

And combining the default plug-in list configuration and the actual plug-in list configuration according to the steps to obtain the fusion plug-in list configuration, so that the ideal plug-in version information (which refers to the version number set by a research and development team according to the actual development requirement) of the plug-in to be managed in the plug-in list to be managed can be determined from the version configuration items by traversing the fusion plug-in list configuration, and therefore, the version number in the default download link is replaced by the ideal plug-in version information, and the spliced target download link of the plug-in to be managed can be obtained. In this way, consistency of plug-in versions can be achieved, thereby reducing the possibility of code conflicts.

S205: and judging whether the plug-in to be managed is installed in the code editor or not according to the plug-in name of the plug-in to be managed, and managing the plug-in to be managed according to the judgment result and the target download link.

After the target download link of the plug-in to be managed is obtained, the plug-in to be managed can be managed only by downloading and installing the plug-in to be managed based on the target download link, however, if the plug-in to be managed is installed in the code editor, the installed plug-in to be managed also needs to be judged. As shown in fig. 3, fig. 3 is a sub-flow diagram of a plug-in management method provided in the embodiment of the present application.

S301: and starting.

S302: and judging whether the plug-in to be managed is installed in the code editor or not.

And the code editor traverses the background to judge whether the plug-in name of the plug-in to be managed exists or not, and can judge whether the plug-in to be managed is installed in the code editor or not based on the plug-in name of the plug-in to be managed.

If the determination result indicates that the plug-in to be managed is installed in the code editor, S303 is executed.

If the judgment result indicates that the plug-in to be managed is not installed in the code editor, S307 is executed.

S303: and acquiring the current plug-in version information of the installed plug-in to be managed.

Because the plug-in to be managed is installed in the code editor, in order to further judge whether the plug-in version of the installed plug-in to be managed meets the requirements of a research and development team, the current plug-in version information of the installed plug-in to be managed needs to be acquired.

S304: traversing the configuration of the fused plug-in list, and determining the ideal plug-in version information of the plug-in to be managed from the version configuration items configured by the fused plug-in list.

Through traversing the configuration of the fusion plug-in list, the ideal plug-in version information (referring to the version number set by a research and development team according to the actual development requirement) of the plug-in to be managed in the plug-in list to be managed can be determined from the version configuration item.

S305: and judging whether the version information of the current plug-in is consistent with the version information of the ideal plug-in.

And comparing and judging whether the version information of the current plug-in is consistent with the version information of the ideal plug-in, and managing the plug-in to be managed according to the judgment result and the target download link.

And if the judgment result represents that the current plug-in version information is consistent with the ideal plug-in version information, executing S306.

S306: the current download of the plug-in to be managed is skipped.

If the current plug-in version information is consistent with the ideal plug-in version information, the plug-in to be managed installed in the code editor meets the requirements of a research and development team, and the plug-in to be managed does not need to be downloaded and installed again, so that the current downloading of the plug-in to be managed in the plug-in list to be managed is skipped directly.

And if the judgment result represents that the current plug-in version information is inconsistent with the ideal plug-in version information, executing S307.

S307: and downloading the plug-in to be managed based on the target download link.

If the current plug-in version information is inconsistent with the ideal plug-in version information, the plug-in to be managed which is installed in the code editor does not meet the requirements of a research and development team, and therefore the plug-in to be managed which meets the requirements of the research and development team needs to be downloaded through the target download link spliced in the previous steps.

S308: and judging whether the plug-in to be managed is installed in a silent mode or not.

The silent installation can also be called unattended installation, which means that no user intervention is needed during installation, the installation mode is directly installed according to default settings during installation, and the installation mode can be used after the installation is finished. Because the plug-in list configuration also comprises installation configuration, whether the plug-in to be managed is silent installation can be judged according to the fused plug-in list configuration.

If it is silent installation, execute S309: the installation process is automatically performed in the background.

And if the installation configuration of the plug-in to be managed in the fusion plug-in list configuration is silent installation, acquiring a silent parameter, and automatically executing the installation process of the plug-in to be managed in the background by the code editor based on the silent parameter.

If not, execute 310: and popping up the plug-in installation interface, receiving the touch operation of the user based on the plug-in installation interface, and responding to the touch operation to complete installation.

If the installation configuration of the plug-in to be managed in the fusion plug-in list configuration is silent installation, a plug-in installation interface shown in fig. 4 pops up on a plug-in extension interface of a code editor, fig. 4 is an interface schematic diagram of the plug-in installation interface provided by the embodiment of the application, a plug-in name 1 in fig. 4 is a plug-in name of the plug-in to be managed, a user sends out touch operation through an installation control of the plug-in installation interface, and the code editor responds to the touch operation after receiving the touch operation of the user to complete installation of the plug-in to be managed.

S311: and (6) ending.

In one embodiment, the plug-in management method further supports custom plug-in list configuration in a working state, and includes the following specific steps: receiving list configuration custom operation; and responding to the self-defining operation of the list configuration, and updating the actual plug-in list configuration of the plug-in list to be managed.

In addition, according to the configuration content in the configuration of the fused plug-in list, all plug-ins can be deleted by one key in the embodiment of the application.

It should be noted that the above steps can be integrated into a command (e.g. syncPlugins) in the code editor, and the above steps can be implemented by executing the command.

According to the plug-in management method, the development environment of a development team can be kept consistent, the possibility of code conflict is reduced, code review and code comparison are concentrated on code increase and decrease, and the problem that other problems caused by code formatting or environment are distracted is avoided.

Based on the content of the foregoing embodiments, an embodiment of the present application provides a plug-in management apparatus, which is suitable for a code editor, and specifically, please refer to fig. 5, the apparatus includes:

a first obtaining module 501, configured to obtain a plug-in name of a plug-in to be managed in a plug-in list to be managed;

a configuration reading module 502, configured to read a default plug-in list configuration and an actual plug-in list configuration of the to-be-managed plug-in list;

a configuration merging module 503, configured to merge the default plugin list configuration and the actual plugin list configuration to obtain a fusion plugin list configuration;

a link splicing module 504, configured to traverse the configuration of the fusion plug-in list, and splice the target download link of the plug-in to be managed according to the version information of the ideal plug-in the configuration of the fusion plug-in list;

and the management module 505 is configured to determine whether the plug-in to be managed is installed in the code editor according to the plug-in name of the plug-in to be managed, and manage the plug-in to be managed according to the determination result and the target download link.

In one embodiment, the configuration merging module 503 includes:

the configuration creating module is used for creating initial plug-in list configuration;

the configuration comparison module is used for comparing the default plug-in list configuration with the actual plug-in list configuration and determining a conflict configuration item and a non-conflict configuration item;

a first determining module, configured to use the configuration of the conflicting configuration item in the actual plug-in list configuration as a target configuration of the conflicting configuration item;

the second determining module is used for determining the target configuration of the non-conflict configuration item according to the default plug-in list configuration and the actual plug-in list configuration;

and the configuration updating module is used for updating the initial plug-in list configuration according to the target configuration of the conflict configuration item and the target configuration of the non-conflict configuration item to obtain the fusion plug-in list configuration.

In one embodiment, the link splicing module 504 includes:

the first acquisition module is used for acquiring the default download link of the plug-in to be managed;

the configuration traversing module is used for traversing the configuration of the fusion plug-in list and determining the ideal plug-in version information of the plug-in to be managed from the version configuration items of the configuration of the fusion plug-in list;

and the splicing submodule is used for splicing to obtain the target download link of the plug-in to be managed according to the default download link and the ideal plug-in version information of the plug-in to be managed.

In one embodiment, the management module 505 comprises:

the second obtaining module is used for obtaining the current plugin version information of the installed plugin to be managed if the judging result represents that the plugin to be managed is installed in the code editor;

the third determining module is used for traversing the configuration of the fused plug-in list and determining the ideal plug-in version information of the plug-in to be managed from the version configuration item configured by the fused plug-in list;

and the first judgment module is used for judging whether the version information of the current plug-in is consistent with the version information of the ideal plug-in and managing the plug-in to be managed according to a judgment result and the target download link.

In one embodiment, the first determining module comprises:

the skip downloading module is used for skipping the current downloading of the plug-in to be managed if the judgment result represents that the version information of the current plug-in is consistent with the version information of the ideal plug-in;

the plug-in downloading module is used for downloading the plug-in to be managed based on the target downloading link if the judgment result represents that the version information of the current plug-in is inconsistent with the version information of the ideal plug-in;

the second judgment module is used for judging whether the plug-in to be managed is installed in a silent mode according to the configuration of the fusion plug-in list;

the silent installation module is used for automatically executing the installation process in the background if the silent installation is carried out;

and the touch control installation module is used for popping up a plug-in installation interface if the installation is not silent, receiving the touch control operation of a user based on the plug-in installation interface, and responding the touch control operation to finish the installation.

In one embodiment, the management module 505 further comprises:

the plug-in downloading module is also used for downloading the plug-in to be managed based on the target downloading link if the judgment result represents that the plug-in to be managed is not installed in the code editor;

the second judging module is also used for judging whether the plug-in to be managed is installed in a silent mode according to the configuration of the fusion plug-in list;

and the touch control installation module is used for popping up a plug-in installation interface if the installation is not silent, receiving the touch control operation of a user based on the plug-in installation interface, and responding to the touch control operation to finish the installation.

In one embodiment, the plug-in management apparatus further comprises:

the operation receiving module is used for receiving the self-defining operation of list configuration;

and the operation response module is used for responding to the self-defining operation of the list configuration and updating the actual plug-in list configuration of the plug-in list to be managed.

Different from the current technology, the plug-in management device provided by the application is provided with the first acquisition module and the configuration merging module, the list of the plug-ins to be managed is acquired through the first acquisition module, the batch installation of the plug-ins to be managed is realized, the target download link of the plug-ins to be managed is obtained through the configuration merging module according to the ideal plug-in version information configured by the fused plug-in list, the automatic update of the plug-ins is avoided based on the plug-in version information, the synchronization of the plug-ins is realized, the development environment consistent with a research and development team is ensured, the possibility of code conflict is reduced, the code review and comparison can be more focused on the code, other problems caused by code formatting or environment are not analyzed, and the development efficiency is improved.

Accordingly, an electronic device may include, as shown in fig. 6, a processor 601 having one or more processing cores, a Wireless Fidelity (WiFi) module 602, a memory 603 having one or more computer-readable storage media, an audio circuit 604, a display unit 605, an input unit 606, a sensor 607, a power supply 608, and a Radio Frequency (RF) circuit 609. Those skilled in the art will appreciate that the configuration of the electronic device shown in fig. 6 does not constitute a limitation of the electronic device and may include more or fewer components than shown, or some components may be combined, or a different arrangement of components. Wherein:

the processor 601 is a control center of the electronic device, connects various parts of the whole electronic device by using various interfaces and lines, and performs various functions of the electronic device and processes data by running or executing software programs and/or modules stored in the memory 603 and calling data stored in the memory 603, thereby performing overall monitoring of the electronic device. In one embodiment, processor 601 may include one or more processing cores; preferably, the processor 601 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 601.

WiFi belongs to short-range wireless transmission technology, and the electronic device can help the user send and receive e-mail, browse web pages, access streaming media, etc. through the wireless module 602, and it provides wireless broadband internet access for the user. Although fig. 6 shows the wireless module 602, it is understood that it does not belong to the essential constitution of the terminal, and may be omitted entirely as needed within the scope not changing the essence of the invention.

The memory 603 may be used to store software programs and modules, and the processor 601 executes various functional applications and data processing by operating the computer programs and modules stored in the memory 603. The memory 603 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the terminal, etc. Further, the memory 603 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device. Accordingly, the memory 603 may also include a memory controller to provide the processor 601 and the input unit 606 access to the memory 603.

The audio circuitry 604 includes speakers that can provide an audio interface between the user and the electronic device. The audio circuit 604 may transmit the electrical signal converted from the received audio data to a speaker, and the audio signal is converted into a sound signal by the speaker and output.

The display unit 605 may be used to display information input by or provided to the user and various graphic user interfaces of the terminal, which may be configured of graphics, text, icons, video, and any combination thereof. The Display unit 605 may include a Display panel, and in one embodiment, the Display panel may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like. Further, the touch-sensitive surface may overlay the display panel, and when a touch operation is detected on or near the touch-sensitive surface, the touch operation is transmitted to the processor 601 to determine the type of the touch event, and then the processor 601 provides a corresponding visual output on the display panel according to the type of the touch event. Although in FIG. 6 the touch sensitive surface and the display panel are implemented as two separate components for input and output functions, in some embodiments the touch sensitive surface may be integrated with the display panel for input and output functions.

The input unit 606 may be used to receive input numeric or character information and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control. Specifically, in one particular embodiment, input unit 606 may include a touch-sensitive surface as well as other input devices. The touch-sensitive surface, also referred to as a touch display screen or a touch pad, may collect touch operations by a user (such as operations by the user on or near the touch-sensitive surface using a finger, a stylus, or any other suitable object or attachment) thereon or nearby, and drive the corresponding connection device according to a predetermined program. In one embodiment, the touch sensitive surface may comprise two parts, a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 601, and can receive and execute commands sent by the processor 601. In addition, touch sensitive surfaces may be implemented using various types of resistive, capacitive, infrared, and surface acoustic waves. The input unit 606 may include other input devices in addition to a touch-sensitive surface. In particular, other input devices may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like.

The electronic device may further include at least one sensor 607, such as a light sensor, specifically, the light sensor may include an ambient light sensor and a distance sensor, wherein the ambient light sensor may adjust the brightness of the display panel according to the brightness of ambient light; as for other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor, which may be further configured to the electronic device, detailed descriptions thereof are omitted.

The electronic device further includes a power supply 608 (e.g., a battery) for providing power to the various components, which is preferably logically connected to the processor 601 via a power management system, such that the power management system can manage charging, discharging, and power consumption. The power supply 608 may also include any component including one or more dc or ac power sources, recharging systems, power failure detection circuitry, power converters or inverters, power status indicators, and the like.

The rf circuit 609 may be configured to receive and transmit signals during a message transmission or communication process, and in particular, receive downlink information of a base station and then send the received downlink information to one or more processors 601; in addition, data relating to uplink is transmitted to the base station. In general, the radio frequency circuitry 609 includes, but is not limited to, an antenna, at least one Amplifier, a tuner, one or more oscillators, a Subscriber Identity Module (SIM) card, a transceiver, a coupler, a Low Noise Amplifier (LNA), a duplexer, and the like. In addition, the radio 609 may also communicate with networks and other devices via wireless communication. The wireless communication may use any communication standard or protocol, including but not limited to Global System for Mobile communications (GSM), general Packet Radio Service (GPRS), code Division Multiple Access (CDMA), wideband Code Division Multiple Access (WCDMA), long Term Evolution (LTE), email, short Message Service (SMS), and the like.

Although not shown, the electronic device may further include a camera, a bluetooth module, and the like, which are not described in detail herein. Specifically, in this embodiment, the processor 601 in the electronic device loads the executable file corresponding to the process of one or more application programs into the memory 603 according to the following instructions, and the processor 601 runs the application programs stored in the memory 603, thereby implementing the following functions:

acquiring the name of a plug-in to be managed in a plug-in list to be managed;

It will be understood by those skilled in the art that all or part of the steps of the methods of the above embodiments may be performed by instructions or by associated hardware controlled by the instructions, which may be stored in a computer readable storage medium and loaded and executed by a processor.

To this end, the embodiment of the present application provides a computer-readable storage medium, in which a plurality of instructions are stored, where the instructions can be loaded by a processor to implement the functions of the above-mentioned plug-in management method.

Wherein the computer-readable storage medium may include: read Only Memory (ROM), random Access Memory (RAM), magnetic or optical disks, and the like.

The method, the apparatus, the electronic device, and the computer-readable storage medium for managing the plug-in provided in the embodiments of the present application are described in detail above, and a specific example is applied in the present application to explain the principles and embodiments of the present application, and the description of the above embodiments is only used to help understand the method and the core idea of the present application; meanwhile, for those skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.

Claims

1. A plug-in management method adapted for use with a code editor, the method comprising:

2. The plugin management method according to claim 1, wherein the step of merging the default plugin list configuration and the actual plugin list configuration to obtain a fused plugin list configuration includes:

creating an initial plug-in list configuration;

comparing the default plug-in list configuration with the actual plug-in list configuration, and determining conflict configuration items and non-conflict configuration items;

taking the configuration of the conflict configuration item in the actual plug-in list configuration as the target configuration of the conflict configuration item;

determining the target configuration of the non-conflict configuration item according to the default plug-in list configuration and the actual plug-in list configuration;

and updating the initial plug-in list configuration according to the target configuration of the conflict configuration item and the target configuration of the non-conflict configuration item to obtain a fusion plug-in list configuration.

3. The plugin management method according to claim 1, wherein the step of traversing the fused plugin list configuration and splicing the target download link of the plugin to be managed according to ideal plugin version information in the fused plugin list configuration includes:

acquiring a default download link of the plug-in to be managed;

traversing the configuration of the fusion plug-in list, and determining the ideal plug-in version information of the plug-in to be managed from the version configuration item configured by the fusion plug-in list;

and splicing to obtain the target download link of the plug-in to be managed according to the default download link and the ideal plug-in version information of the plug-in to be managed.

4. The plug-in management method according to claim 1, wherein the step of judging whether the plug-in to be managed is installed in the code editor or not according to the plug-in name of the plug-in to be managed and managing the plug-in to be managed according to the judgment result and the target download link comprises:

if the judgment result represents that the plug-in to be managed is installed in the code editor, current plug-in version information of the installed plug-in to be managed is obtained;

traversing the configuration of the fusion plug-in list, and determining the ideal plug-in version information of the plug-in to be managed from the version configuration items of the configuration of the fusion plug-in list;

and judging whether the version information of the current plug-in is consistent with the version information of the ideal plug-in, and managing the plug-in to be managed according to a judgment result and the target download link.

5. The plug-in management method according to claim 4, wherein the step of judging whether the installation version information and the plug-in version information are consistent and managing the plug-in to be managed according to the judgment result and the target download link comprises:

if the judgment result represents that the current plugin version information is consistent with the ideal plugin version information, skipping the current downloading of the plugin to be managed;

if the judgment result represents that the current plug-in version information is inconsistent with the ideal plug-in version information, downloading the plug-in to be managed based on the target download link;

judging whether the plug-in to be managed is installed in a silent mode or not according to the configuration of the fusion plug-in list;

if the installation is silent, automatically executing an installation process in the background;

and if the installation is not silent, popping up a plug-in installation interface, receiving the touch operation of the user based on the plug-in installation interface, and responding to the touch operation to finish the installation.

6. The plug-in management method according to claim 1, wherein the step of judging whether the plug-in to be managed is installed in the code editor or not according to the plug-in name of the plug-in to be managed and managing the plug-in to be managed according to the judgment result and the target download link comprises:

if the judgment result represents that the plug-in to be managed is not installed in the code editor, downloading the plug-in to be managed based on the target download link;

and if the installation is not silent, popping up a plug-in installation interface, receiving touch operation of a user based on the plug-in installation interface, and responding to the touch operation to finish installation.

7. The plug-in management method according to claim 1, further comprising:

receiving list configuration custom operation;

and responding to the list configuration custom operation, and updating the actual plug-in list configuration of the plug-in list to be managed.

8. A plug-in management apparatus adapted for use with a code editor, the apparatus comprising:

and the management module is used for judging whether the plug-in to be managed is installed in the code editor or not according to the plug-in name of the plug-in to be managed and managing the plug-in to be managed according to a judgment result and the target download link.

9. An electronic device comprising a processor and a memory, the memory being configured to store a computer program, the processor being configured to execute the computer program in the memory to perform the steps of the plug-in management method of any one of claims 1 to 7.

10. A computer-readable storage medium storing instructions adapted to be loaded by a processor to perform the steps of the plug-in management method according to any one of claims 1 to 7.