Method and device for realizing front-end management based on code repository, equipment and medium

Abstract

The invention relates to the field of development assistance and the field of financial science and technology, and discloses a method, a device, equipment and a medium for realizing front-end management based on a code warehouse, which comprises the following steps: acquiring a front-end project development scene, analyzing public content requirements to determine categories and carding to obtain a list, and constructing a double-warehouse management mechanism comprising a public warehouse and a business warehouse based on the list, performing version control on public warehouse contents to obtain information, analyzing development efficiency and code quality according to a double-warehouse management mechanism and the version control information, calculating an overall performance index, evaluating a development effect, identifying positive and negative factors therein, analyzing a project architecture, and formulating an optimization strategy; and optimizing the project based on the optimization strategy to obtain an optimized project, analyzing a project target and generating a front-end management scheme. And the front-end management efficiency is improved.

Description

Technical Field

[0001] The present invention relates to the field of development assistance and financial technology, and in particular to a method, device, equipment and medium for implementing front-end management based on a code repository. Background Art

[0002] In today's software development and financial technology fields, as project scale continues to expand and complexity increases, the importance of front-end management has become increasingly prominent. In the field of financial technology, front-end development involves many key aspects, such as the construction of project scaffolding for financial trading platforms, which needs to ensure its stability and efficiency to meet the needs of high-frequency trading; the design of public methods must take into account the security and accuracy of financial data processing, such as the application of encryption algorithms, data verification mechanisms, etc.; in terms of components, including various financial chart components, trading interface components, etc., their management level directly affects development efficiency and project quality.

[0003] At present, the traditional front-end management methods have the following main problems: on the one hand, project templates that rely on code hosting platforms or npm packages are only provided at the beginning of project creation and cannot be flexibly applied in the project life cycle, limiting their role in continuous development and maintenance; on the other hand, the way of managing public methods and components through npm cannot fully cover more complex technical solutions such as project scaffolding, resulting in incomplete public content management and affecting the overall efficiency of the project. Therefore, a front-end management method based on code repositories is needed to improve front-end management efficiency. Summary of the invention

[0004] The present invention provides a method, device, equipment and medium for implementing front-end management based on a code repository to improve front-end management efficiency.

[0005] In a first aspect, a method for implementing front-end management based on a code repository is provided, including:

[0006] Obtaining a development scenario corresponding to a front-end project, analyzing public content requirements in the development scenario, determining public content categories in the development scenario based on the public content requirements, sorting out the public content categories, and obtaining a public content list;

[0007] Based on the public content list, a dual warehouse management mechanism corresponding to the front-end project is constructed, and version control is performed on the public content in the public warehouse of the dual warehouse management mechanism to obtain version control information;

[0008] Based on the dual warehouse management mechanism and version control information, the development efficiency and code quality corresponding to the front-end project are analyzed, and according to the development efficiency and the code quality, the overall performance index corresponding to the front-end project is calculated, and based on the overall performance index, the development effect corresponding to the front-end project is evaluated;

[0009] Identify positive factors and negative factors in the development effect, analyze the project architecture corresponding to the front-end project based on the positive factors and the negative factors, and formulate an optimization strategy for the front-end project based on the project architecture;

[0010] Based on the optimization strategy, the front-end project is optimized to obtain an optimized project, the project goal corresponding to the optimized project is analyzed, and based on the project goal, a front-end management plan corresponding to the front-end project is generated.

[0011] In a second aspect, a device for implementing front-end management based on a code repository is provided, including:

[0012] A content combing module is used to obtain the development scenario corresponding to the front-end project, analyze the public content requirements in the development scenario, determine the public content category in the development scenario based on the public content requirements, comb the content of the public content category, and obtain a public content list;

[0013] A version control module, used to build a dual warehouse management mechanism corresponding to the front-end project based on the public content list, and perform version control on the public content in the public warehouse of the dual warehouse management mechanism to obtain version control information;

[0014] An effect evaluation module, used to analyze the development efficiency and code quality corresponding to the front-end project based on the dual warehouse management mechanism and version control information, calculate the overall performance index corresponding to the front-end project according to the development efficiency and the code quality, and evaluate the development effect corresponding to the front-end project based on the overall performance index;

[0015] A strategy formulation module, used to identify positive factors and negative factors in the development effect, analyze the project architecture corresponding to the front-end project based on the positive factors and the negative factors, and formulate an optimization strategy for the front-end project based on the project architecture;

[0016] The solution generation module is used to optimize the front-end project based on the optimization strategy to obtain the optimized project, analyze the project goals corresponding to the optimized project, and generate a front-end management solution corresponding to the front-end project based on the project goals.

[0017] In a third aspect, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the above-mentioned method for front-end management based on a code repository when executing the computer program.

[0018] In a fourth aspect, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method for implementing front-end management based on a code repository is implemented.

[0019] Compared with the problems described in the background technology, firstly, the present invention obtains the development scenario corresponding to the front-end project and analyzes the public content needs in the development scenario, so as to accurately understand the specific environment and business requirements of the project. It is like drawing a clear background blueprint for the project, which can accurately grasp which parts of the project can be shared and reused, avoid duplication of development work, and thus improve development efficiency. Secondly, based on the public content list, the present invention constructs a dual warehouse management mechanism corresponding to the front-end project, which can achieve more refined management of public content, and can perform independent version iteration and release strategy formulation according to their respective characteristics and needs, making the overall management of the project more flexible and efficient, thereby improving the development quality and delivery speed of the front-end project, and better adapting to the ever-changing business needs and technical environment. Then, based on the dual warehouse management mechanism and version control information, the present invention divides Analyze the development efficiency and code quality corresponding to the front-end project, and the analysis can accurately evaluate the actual performance in the project development process, which is helpful to find the bottlenecks and obstacles in the process, so as to optimize and improve it in a targeted manner, and can timely find potential defects and risks to ensure the stability and reliability of the project. Further, the present invention can serve as a motivation point for the team by identifying the positive and negative factors in the development effect, enhance the team's self-confidence and sense of accomplishment, promote better collaboration between team members, and can replicate and promote these successful experiences to subsequent projects to improve the overall development capabilities. Finally, based on the optimization strategy, the present invention optimizes the front-end project to obtain an optimized project, which can provide a faster, smoother and more convenient interactive experience, reduce memory usage and CPU consumption, and reduce the risk of the project being stuck or crashing in high-concurrency scenarios. This enables the project to better cope with large-scale user access and ensure the continuity and reliability of the business. Therefore, the method, device, equipment and medium for implementing front-end management based on the code warehouse proposed in the present invention can improve the efficiency of front-end management. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0021] Figure 1 This is a schematic diagram of an application environment of a method for implementing front-end management based on a code repository in one embodiment of the present invention;

[0022] Figure 2 It is a flow chart of a method for implementing front-end management based on a code repository in one embodiment of the present invention;

[0023] Figure 3 It is a structural diagram of a device for implementing front-end management based on a code repository in one embodiment of the present invention;

[0024] Figure 4 is a schematic diagram of a structure of a computer device in one embodiment of the present invention;

[0025] Figure 5 It is another structural schematic diagram of a computer device in one embodiment of the present invention. DETAILED DESCRIPTION

[0026] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0027] The method for implementing front-end management based on code repository provided by the embodiment of the present invention can be applied in the following aspects: Figure 1In an application environment, the client communicates with the server through a network. The server can obtain the development scenario corresponding to the front-end project through the client, analyze the public content requirements in the development scenario, determine the public content category in the development scenario based on the public content requirements, sort out the content of the public content category, and obtain a public content list; based on the public content list, build a dual warehouse management mechanism corresponding to the front-end project, and perform version control on the public content in the public warehouse of the dual warehouse management mechanism to obtain version control information; based on the dual warehouse management mechanism and version control information, analyze the development efficiency and code quality corresponding to the front-end project, calculate the overall performance index corresponding to the front-end project according to the development efficiency and the code quality, and evaluate the development effect corresponding to the front-end project based on the overall performance index; identify the positive and negative factors in the development effect, analyze the project architecture corresponding to the front-end project based on the positive and negative factors, and formulate the optimization strategy of the front-end project based on the project architecture; based on the optimization strategy, optimize the front-end project to obtain an optimized project, analyze the project goals corresponding to the optimized project, and generate the front-end management plan corresponding to the front-end project based on the project goals. The client may be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, and portable wearable devices. The server may be implemented by an independent server or a server cluster consisting of multiple servers. The present invention is described in detail below through specific embodiments.

[0028] See also Figure 2 As shown, Figure 2 A flowchart of a method for implementing front-end management based on a code repository provided by an embodiment of the present invention includes the following steps:

[0029] S1. Obtain a development scenario corresponding to a front-end project, analyze public content requirements in the development scenario, determine public content categories in the development scenario based on the public content requirements, sort out the public content categories, and obtain a public content list.

[0030] The present invention obtains the development scenario corresponding to the front-end project and analyzes the public content needs in the development scenario, so as to accurately understand the specific environment and business requirements of the project. It is like drawing a clear background blueprint for the project, which can accurately grasp which parts of the project can be shared and reused, avoid duplication of development work, and thus improve development efficiency.

[0031] Among them, the development scenario refers to a specific development situation composed of comprehensive factors such as the specific situations, business fields, application types involved in the development process of the front-end project, and various technical and non-technical environments faced by the project, which covers the target user group of the project, usage scenarios, functional requirements, technical architecture requirements, interaction modes with the back-end system and other aspects; the public content requirements refer to the content requirements in the front-end project that can be used and shared by multiple modules, functions or pages in a specific development scenario, including but not limited to common interface components (such as buttons, forms, navigation bars, etc.), common business logic methods (such as data validation, encryption and decryption algorithms, etc.), common styles and layout specifications, common tool functions and infrastructure-related requirements such as project scaffolding. Optionally, the acquisition of the development scenario corresponding to the front-end project can be achieved through project management tools, such as Jira, Trello and other tools, and the analysis of the public content requirements in the development scenario can be achieved through functional decomposition, such as decomposing the various functional modules in the development scenario and finding the repeated parts as public content requirements.

[0032] Furthermore, the present invention determines the public content category in the development scenario based on the public content demand, which can organize and manage project resources more efficiently, avoid chaotic allocation and repeated investment of resources, help improve code reusability, reduce unnecessary development work, speed up project development progress, ensure project stability and sustainability, thereby improving the quality and competitiveness of front-end projects as a whole.

[0033] Among them, the public content category refers to a collection of different types obtained by dividing according to certain standards or characteristics based on the public content needs in the front-end project development scenario, which may include interface component categories, such as common button components, input box components, menu components, etc., which may be frequently used in multiple pages or functional modules; there are also public business logic categories, such as user identity authentication logic, data encryption and decryption logic, data paging loading logic, etc. Optionally, the determination of the public content category in the development scenario can be achieved through a functional similarity classification method, such as: in the front-end project, all requirements related to data display, such as table display, chart display, list display, etc. can be classified into the "data display category" public content category.

[0034] Furthermore, the present invention combs the content of the public content categories to obtain a public content list, which can accurately identify the specific elements contained in each public content category, which helps to improve resource utilization in the development process and avoid duplication of work and waste of resources. For example, when developing multiple pages, it is possible to clearly identify which components, functions or styles can be reused and call them directly from the public content list, greatly improving development efficiency.

[0035] Among them, the public content list refers to a detailed list document generated after comprehensive sorting and analysis of public content categories, which covers various aspects of public content categories, including category name, detailed description of each specific content element (such as function description, attribute list, usage examples, etc.), grouping of similar content items, and the overall application architecture and association relationships of these public contents in the front-end project.

[0036] As an embodiment of the present invention, the content combing of the public content category to obtain a public content list includes: analyzing functional attributes corresponding to the public content category; determining content combing rules corresponding to the functional attributes; based on the content combing rules, screening specific content elements corresponding to the public content category; classifying similar content items corresponding to the specific content elements; and generating a public content list corresponding to the public content category based on the classified similar content items.

[0037] Among them, the functional attributes refer to the specific functions and related characteristics of the public content category in the front-end project. For example, for the public content of the interface component category of the financial trading platform, its functional attributes may include the interactive functions of the components, such as the response speed and accuracy when the user clicks the transaction button, to ensure that the transaction instructions can be sent in a timely and accurate manner; in terms of display function, it is necessary to clearly present the real-time prices, trend charts and other information of financial products; the layout characteristics need to consider how to reasonably arrange the various components on the trading interface, such as the position, size and arrangement of the order input box and transaction confirmation button; the content combing rules refer to a series of criteria and methods for organizing and classifying public content based on the functional attributes of the public content category. For example, if it is classified according to the interaction type (such as fingerprint recognition login components with a higher security level, pop-up components for risk warnings, etc.); for the public business logic category, if the functional attributes focus on the security and accuracy of the data, the content combing rules may be based on the data The specific content elements are sorted by the strictness of verification or the complexity of data processing; the specific content elements refer to the actual individual units that constitute the common content categories, which have clear functions and specific attributes. In the interface component category, the specific content element may be a specific button component with its own style, event processing function, position in the page and other attributes; in the public business logic category, the specific content element may be a specific data verification function, which contains specific content such as input parameters, verification logic and return value; the similar content items refer to a group of content items in the specific content elements that are similar in function, characteristic or structure. For example, in the interface component category, several button components with similar appearance and similar functions (such as submit button, confirm button, etc.) can be classified as similar content items; in the public business logic category, functions that perform similar data calculation operations (such as different addition operation functions, although the data objects processed may be different, the operation logic is similar) can also be regarded as similar content items.

[0038] Furthermore, the analysis of the functional attributes corresponding to the public content category can be implemented through a prototype design tool, such as Axure, Sketch and other tools; the determination of the content combing rules corresponding to the functional attributes can be implemented through a decision tree algorithm, such as building a decision tree based on the functional attributes, each node represents a judgment condition of a functional attribute, and the branches represent different combing rules; the screening of specific content elements corresponding to the public content category can be implemented through a code review method, such as directly reviewing the code of the front-end project, and screening out the corresponding specific content elements according to the definition and characteristics of the public content category; the classification of similar content items corresponding to the specific content elements can be implemented through a feature comparison method, such as comparing various features of specific content elements, such as functional characteristics, code structure, style attributes, etc., and classifying elements with similar features into one category; the generation of a public content list corresponding to the public content category can be implemented through a template filling method, such as first formulating a template for a public content list, and then filling the corresponding information into the template according to the combing results.

[0039] S2. Based on the public content list, a dual warehouse management mechanism corresponding to the front-end project is constructed, and version control is performed on the public content in the public warehouse of the dual warehouse management mechanism to obtain version control information.

[0040] Based on the public content list, the present invention constructs a dual warehouse management mechanism corresponding to the front-end project, which can achieve more refined management of public content. Independent version iteration and release strategy formulation can be performed according to their respective characteristics and needs, making the overall management of the project more flexible and efficient, thereby improving the development quality and delivery speed of the front-end project, and better adapting to the ever-changing business needs and technical environment.

[0041] The dual warehouse management mechanism refers to a management mode used in front-end project management to store project-related content in two different warehouses. The mechanism aims to achieve more efficient and organized project development and maintenance by distinguishing different types of content. The dual warehouse management mechanism includes public warehouses and business warehouses. Specifically, the public warehouse refers to a warehouse dedicated to storing public content in front-end projects. These public contents are universal and reusable and can be shared by multiple business modules or different scenarios in the project. For example, common public components (such as button components, navigation bar components, etc.), public styles (such as global font styles, color themes, etc.), and public business logic Logical functions (such as data validation functions, general encryption and decryption functions, etc.) and infrastructure-related content such as project scaffolding can be stored in the public warehouse; the business warehouse refers to a warehouse used to store content directly related to specific business functions in front-end projects. It contains code, data and related resources for implementing the unique functions and business logic of each specific business module. Each business module has its own specific business requirements and processes. The content in the business warehouse is customized to meet these requirements. For example, in the front-end project of an e-commerce platform, the business warehouse may contain the specific logic of the product display page, the implementation code of the shopping cart function, the interface and logic related to the order processing process, etc.

[0042] Furthermore, the dual warehouse management mechanism corresponding to the construction of the front-end project can be implemented through a mechanism construction tool, such as using the Webpack tool to set different entry points and output paths to distinguish between public warehouses and business warehouses.

[0043] The present invention performs version control on the public content in the public warehouse to obtain version control information, thereby ensuring the traceability of the public content. When a problem occurs during the development of a front-end project or a rollback to a specific version is required, the previous stable state can be quickly located through the version control information, which greatly reduces the time cost of troubleshooting and restoring the project, and can ensure that the correct public content version is used in different environments, thereby improving the stability and reliability of the project.

[0044] Among them, the version control information refers to a collection of related information generated by performing version control operations on public content, including version numbers, detailed records of version control data (such as code changes, file additions or deletions for each submission), key point marks and descriptions, branch and tag management information, and other version-related metadata (such as author, submission time, merge records, etc.).

[0045] As an embodiment of the present invention, the version control of the public content in the public warehouse of the dual warehouse management mechanism to obtain version control information includes: analyzing the public content structure in the public warehouse of the dual warehouse management mechanism; determining the version control strategy corresponding to the public content structure; creating a version control environment corresponding to the public warehouse based on the version control strategy; collecting version control data in the version control environment; marking the version number and key points corresponding to the version control data; and performing version control on the public content in the public warehouse based on the version number and the key points to obtain version control information.

[0046] The public content structure refers to the organizational form and composition of the public content in the public repository, which includes the various elements contained in the public content, such as the types and hierarchical relationships of interface components, the classification and calling relationships of public business logic functions, the layout and association of public style files, etc.; the version control strategy refers to a series of rules and methods for managing and controlling versions formulated based on the characteristics of the public content in the public repository and project requirements, including selecting a suitable version control system (such as Git, SVN, etc.), determining branch management strategies (such as the creation and merging rules of development branches, main branches, and feature branches), defining the use of tags (used to mark important versions or milestones), and formulating code submission and review. process, etc.; the version control data refers to the various data involved in the version control process, including code files of public content, resource files (such as images, audio, etc.), configuration files and version-related metadata (such as submission logs, author information, timestamps, etc.); the version number refers to a unique identifier used to identify different versions of public content, which usually adopts certain naming rules so that it can clearly reflect the sequence and importance of the versions; the key points refer to content nodes or features that are of great significance or require special attention in the version control process, which may include important functional changes of public content, key code modification points, repairs of major problems and events related to project milestones, etc.

[0047] Furthermore, the analysis of the public content structure in the public warehouse can be achieved through a directory structure analysis method, such as: inferring the structure of the public content by analyzing the directory structure of the public warehouse; the determination of the version control strategy corresponding to the public content structure can be achieved through a project requirement analysis method, such as: determining the version control strategy according to the requirements of the front-end project; the creation of a version control environment corresponding to the public warehouse can be achieved through a version control platform, such as: GitHub, GitLab and other tools; the collection of version control data in the version control environment can be achieved through a data collection script, such as: writing a script to connect to the API of the version control warehouse or using a command line tool to collect the required version control data; the marking of the version number and key points corresponding to the version control data can be achieved through a version number generation algorithm, such as: an algorithm can be designed to automatically generate a semantic version number according to the code changes and the project's version control strategy; the version control of the public content in the public warehouse can be achieved through a version control system, such as: Git, SVN and other systems.

[0048] S3. Based on the dual warehouse management mechanism and version control information, analyze the development efficiency and code quality corresponding to the front-end project, calculate the overall performance indicators corresponding to the front-end project according to the development efficiency and the code quality, and evaluate the development effect corresponding to the front-end project based on the overall performance indicators.

[0049] The present invention analyzes the development efficiency and code quality corresponding to the front-end project based on the dual warehouse management mechanism and version control information. The analysis can accurately evaluate the actual performance in the project development process, help to discover bottlenecks and obstacles in the process, and thus perform targeted optimization and improvement. It can also timely discover potential defects and risks to ensure the stability and reliability of the project.

[0050] Among them, the development efficiency refers to the effective amount of work completed per unit time or the speed of achieving specific functional goals during the front-end project development process, which covers the comprehensive efficiency performance of various stages from project planning, design, coding to testing and deployment, including the speed of developers writing code, problem-solving ability, fluency of team collaboration, and efficiency of utilization of development resources. The code quality refers to the quality of the front-end project code, which is reflected in multiple aspects, including the readability of the code, that is, external developers can easily understand the logic and function of the code; maintainability, whether the code is easy to modify, expand and debug, so that it can be easily maintained and upgraded during the life cycle of the project; scalability, whether the code has a good architectural design and can easily adapt to new functional requirements and business changes; reliability, whether the code is stable during operation and can correctly handle various inputs and abnormal situations to avoid errors and crashes; and the standardization of the code, whether it follows industry standards and best practices and maintains a good code style and structure. Optionally, the analysis of the development efficiency and code quality corresponding to the front-end project can be achieved through project management tools, such as Jira, Trello and other tools.

[0051] Furthermore, the present invention calculates the overall performance indicators corresponding to the front-end project based on the development efficiency and the code quality, providing a comprehensive and quantitative evaluation standard for the project, which can clearly compare the advantages and disadvantages of different stages or different projects, and help management make more informed resource allocation and project decisions. It can also clarify whether the performance bottleneck is caused by an overly procrastinating development process or code quality issues, and then make targeted improvements.

[0052] Among them, the overall performance index refers to a quantitative value or a set of related values ​​that can comprehensively reflect the overall operation status and performance of the project after comprehensively considering multiple factors such as the development efficiency of the front-end project during the development process and the quality of the generated code. Optionally, the calculation of the overall performance index corresponding to the front-end project can be achieved through a weighted summation method, such as: assigning weights to each sub-factor of development efficiency and code quality, and then performing weighted summation of the quantitative values ​​of these factors to obtain the overall performance index.

[0053] Furthermore, the present invention evaluates the development effect corresponding to the front-end project based on the overall performance indicators, which can clearly understand whether the project has met the established requirements and the level of competitiveness among similar projects, and help to timely discover the advantages and disadvantages of the project, and provide a clear direction for subsequent improvement and optimization, thereby strengthening the code review and quality control links in a targeted manner.

[0054] Among them, the development effect refers to the comprehensive results and performance achieved by the front-end project during the development process, which covers multiple aspects of the project, including but not limited to the completeness and accuracy of function implementation, the quality of user experience, the level of development efficiency, the quality of code, the stability and reliability of the project, and the degree of satisfaction of business needs.

[0055] As an embodiment of the present invention, the evaluation of the development effect corresponding to the front-end project based on the overall performance indicator includes: analyzing the constituent dimensions corresponding to the overall performance indicator; determining the evaluation criteria corresponding to the constituent dimensions; based on the evaluation criteria, quantitatively scoring the overall performance indicator to obtain a scoring result; screening key scoring points in the scoring result; and evaluating the development effect corresponding to the front-end project based on the key scoring points.

[0056] Among them, the constituent dimensions refer to the various aspects or elements covered by the overall performance indicators, which together constitute the basis for a comprehensive evaluation of the front-end project. For example, the development efficiency dimension may include the time cycle of function development, the smoothness of team collaboration, the timeliness of problem solving, etc.; the code quality dimension may cover aspects such as the standardization, readability, maintainability, reliability and security of the code; the resource utilization dimension may involve the allocation and utilization efficiency of resources such as human, material and time, etc.; the evaluation criteria refer to the specific criteria or specifications used to measure and judge the performance of each constituent dimension in the overall performance indicator; the scoring result refers to the specific value or grade obtained after quantitative evaluation of each constituent dimension in the overall performance indicator according to the determined evaluation criteria, such as a scoring system from 0 to 10 points, or a graded form, such as excellent, good, medium, pass, fail, etc.; the key scoring point refers to the part that performs outstandingly in the scoring result, that is, the constituent dimension or specific indicator with a high score and an important impact on the overall development effect of the front-end project.

[0057] Furthermore, the analysis of the constituent dimensions corresponding to the overall performance indicators can be achieved through a data dictionary tool, such as: using a project-related data dictionary, which records various data elements and business rules, from which the constituent dimensions of the overall performance indicators can be mined; the determination of the evaluation criteria corresponding to the constituent dimensions can be achieved through a hierarchical analysis algorithm, such as: building a hierarchical model through an AHP algorithm, calculating the relative weight of each criterion to determine the evaluation criteria; the quantitative scoring of the overall performance indicators can be achieved through a project evaluation tool, such as: using project evaluation tools such as COCOMO II, quantitative scoring of dimensions such as development efficiency can be performed based on factors such as the scale and complexity of the project; the screening of key scoring points in the scoring results can be achieved through a data visualization tool, such as: inputting the quantitative scoring results into a data visualization tool such as Tableau, and displaying the scores of each dimension in the form of a bar chart, a line chart, etc.; the evaluation of the development effect corresponding to the front-end project can be achieved through a comparative analysis method, such as: comparing and evaluating the development effect of this project with similar projects, historical projects or industry benchmark projects.

[0058] S4. Identify the positive factors and negative factors in the development effect, analyze the project architecture corresponding to the front-end project based on the positive factors and the negative factors, and formulate an optimization strategy for the front-end project based on the project architecture.

[0059] By identifying the positive and negative factors in the development effect, the present invention can serve as a motivation point for the team, enhance the team's self-confidence and sense of accomplishment, promote better collaboration among team members, and can replicate and promote these successful experiences to subsequent projects to improve overall development capabilities.

[0060] Among them, the positive factors refer to those factors that play a positive role in the smooth progress of the project, quality improvement, user experience optimization and team collaboration in the front-end project development effect. They may include efficient development processes, so that the project can complete high-quality functional development in a shorter period of time; excellent code quality, such as strong readability, high maintainability, and clear and reasonable structure of the code, which is conducive to subsequent upgrades and expansions; a good team collaboration atmosphere, with smooth communication, clear division of labor, and mutual support among members, which can efficiently solve problems and complete tasks; effective resource utilization, such as reasonable allocation of human, material and time resources to maximize the value of resources; advanced technology selection and application to improve the performance and function realization of the project; users' high recognition and good feedback on the project functions and interfaces, etc.; the negative factors refer to those factors that have an adverse impact on the project and hinder the development of the front-end project. Factors that slow down project progress, reduce project quality or lead to poor user experience include low development efficiency, such as extended project development cycle and delayed function implementation; code quality issues, such as a large number of vulnerabilities, poor code standardization and low scalability; poor team collaboration, such as communication barriers, frequent conflicts and unclear responsibilities among members; waste or shortage of resources, such as unreasonable allocation of manpower leading to excessive backlog of certain tasks or shortage of key resources affecting key links of the project; improper technology selection leading to project performance bottlenecks or poor compatibility with other systems; negative user feedback, such as complex interface operation, functions that do not meet user expectations, frequent failures, etc. Optionally, the identification of positive and negative factors in the development effect can be achieved through a decision tree algorithm, such as taking various characteristics of the development effect as input, such as development cycle, code error rate, user satisfaction, etc., and constructing a decision tree model to classify positive and negative factors.

[0061] Furthermore, based on the positive factors and the negative factors, the present invention analyzes the project architecture corresponding to the front-end project, and can further study how to implement module division and interface design in the project architecture so that the code can be easily reused, and can adjust and optimize the project architecture in a targeted manner to avoid similar problems from occurring again in future projects.

[0062] Among them, the project architecture refers to the overall structural design and organization of the front-end project, including the layout structure of the front-end page, the division and organization of components, the interaction method between modules, the flow of data, and the interface design with the back-end.

[0063] As an embodiment of the present invention, analyzing the project architecture corresponding to the front-end project based on the positive factors and the negative factors includes: analyzing the factor influence points corresponding to the positive factors and the negative factors; determining the factor analysis direction corresponding to the factor influence points; based on the factor analysis direction, performing a preliminary analysis on the front-end project to obtain preliminary analysis results; screening key architecture features in the preliminary analysis results; and analyzing the project architecture corresponding to the front-end project based on the key architecture features.

[0064] Among them, the factor influencing point refers to the specific position or link where positive factors and negative factors have an impact in the front-end project. For example, efficient code reuse in the positive factor may affect the organization of the code module and the interface design and other influencing points; slow page loading in the negative factor may affect the network request processing, resource loading strategy and other influencing points; the factor analysis direction refers to the specific analysis angle or dimension determined for the factor influencing point. For the factor influencing point of code reuse, the factor analysis direction may include module independence, interface universality, etc.; for the factor influencing point of slow page loading, the factor analysis direction may be network optimization, resource compression, etc.; the preliminary analysis result refers to the result obtained after preliminary analysis of the front-end project based on the determined factor analysis direction, which may include a specific description of the situation of each factor influencing point, statistics of relevant data (such as the coupling degree of the code module, the specific value of the page loading time, etc.) and a preliminary judgment of the problem, etc.; the key architecture feature refers to the key elements extracted from the preliminary analysis results that have an important impact on the project architecture and can reflect the characteristics and problems of the project architecture.

[0065] Further, the analysis of the factor influence points corresponding to the positive factors and negative factors can be achieved through a process tracing method, such as: the positive factor is a good user interaction experience, starting from the user operation interface, tracing back to the event processing function, data acquisition and update process, so as to determine the various links that affect the user experience, such as interface layout, data response time and other factor influence points; the determination of the factor analysis direction corresponding to the factor influence point can be achieved through a goal-oriented method, such as: determining the analysis direction according to the goals of the front-end project (such as high performance, high maintainability, good user experience, etc.); the preliminary analysis of the front-end project can be achieved through a functional decomposition method, such as: decomposing the front-end project according to functional modules, and analyzing the input and output, internal logic, and interaction with other modules of each module; the screening of key architectural features in the preliminary analysis results can be achieved through a feature selection algorithm, such as: using a feature selection algorithm such as the ReliefF algorithm to screen out key architectural features based on the correlation between features and the ability to distinguish targets; the analysis of the project architecture corresponding to the front-end project can be achieved through an architectural pattern recognition method, such as: identifying the architectural patterns (such as MVC, MVVM, etc.) used in the front-end project, and analyzing its application effect in the project.

[0066] The present invention formulates an optimization strategy for the front-end project based on the project architecture, which can accurately identify performance bottlenecks and potential problem points, and then formulate corresponding optimization strategies, such as optimizing data loading methods, improving component communication mechanisms, etc., thereby increasing page loading speed and reducing system response time.

[0067] Among them, the optimization strategy refers to a series of specific action plans and methods formulated according to the optimization direction and project key points determined by analysis in order to improve the current status of the front-end project and achieve the expected optimization goals. It covers specific measures and steps in many aspects such as technology selection adjustment, architecture improvement, code optimization, performance improvement, and user experience enhancement.

[0068] As an embodiment of the present invention, the optimization strategy of the front-end project is formulated based on the project architecture, including: querying the current status corresponding to the project architecture; analyzing the optimization direction corresponding to the current status; based on the optimization direction, collecting the project key points corresponding to the front-end project; based on the project key points, formulating the optimization strategy of the front-end project.

[0069] Among them, the current status refers to the actual situation of the front-end project architecture at the current moment, covering all aspects of the architecture, such as technology selection, component structure, module division, data flow method, performance, and interaction with other systems, including the front-end framework and its version adopted by the project, the functions and responsibilities of each component, the dependencies between modules, the transmission and processing methods of data at different levels and components, and the performance indicators (such as page loading speed, response time, memory usage, etc.), maintainability (code readability, modifiability, scalability, etc.) and user experience of the current project during operation. The optimization direction refers to the specific performance required to improve the project performance, quality, maintainability, etc., based on the analysis of the current status of the project architecture. Goals and focuses to be improved. For example, if the current status shows that the page loading speed is slow, then the optimization direction may be to improve performance, including optimizing network requests, reducing resource file size, improving code loading strategies, etc.; if the code maintainability is poor, the optimization direction may be to enhance the readability and scalability of the code, such as standardizing the code structure, optimizing component design, and improving the independence of modules; the project highlights refer to the important factors or core content that play a key role in achieving project goals, ensuring project quality, and affecting user experience in the front-end project. It may include the core functional modules of the project, key business processes, interface parts where users frequently interact, components or links where performance bottlenecks are located, key nodes of data processing, and key points related to project stability and security.

[0070] Furthermore, the query of the current status corresponding to the project architecture can be achieved through performance monitoring tools, such as: a comprehensive evaluation of the performance of the front-end project can be performed, including page loading speed, resource loading status, accessibility and other aspects; the analysis of the optimization direction corresponding to the current status can be achieved through data analysis platform tools, such as: Mixpanel, GoogleAnalytics and other tools; the collection of project key points corresponding to the front-end project can be achieved through project management tools, such as: Jira, Trello tools; the formulation of the optimization strategy for the front-end project can be achieved through simulation testing tools, such as: Selenium, BrowserStack and other tools.

[0071] S5. Based on the optimization strategy, the front-end project is optimized to obtain an optimized project, the project goal corresponding to the optimized project is analyzed, and based on the project goal, a front-end management plan corresponding to the front-end project is generated.

[0072] Based on the optimization strategy, the present invention optimizes the front-end project to obtain an optimized project, which can provide a faster, smoother and more convenient interactive experience, reduce memory usage and CPU consumption, and reduce the risk of the project being stuck or crashing in high-concurrency scenarios. This enables the project to better cope with large-scale user access and ensure business continuity and reliability.

[0073] Among them, the optimization project refers to the front-end project results finally obtained after comprehensive optimization processing and meeting or exceeding the specific goals set by the optimization strategy. This project has significant improvements in performance, quality, user experience, etc., and has higher stability, reliability and efficiency.

[0074] As an embodiment of the present invention, the front-end project is optimized based on the optimization strategy to obtain the optimized project, including: determining the specific goal corresponding to the optimization strategy; querying the implementation steps corresponding to the specific goal; based on the implementation steps, adjusting the code of the front-end project to obtain an adjusted project code; extracting performance optimization points in the adjusted project code; based on the performance optimization points, optimizing the front-end project to obtain the optimized project.

[0075] The specific goal refers to the specific, measurable results or improvement directions to be achieved through the optimization strategy based on the current situation and needs of the front-end project, for example, shortening the page loading time to less than 2 seconds, improving the maintainability of the code so that the complexity score of the code is reduced by 50%, improving the fluency of user interaction so that the response time of user operations is reduced by 30%, and other specific performance, quality or user experience goals; the implementation steps refer to a series of detailed and orderly operation processes and action plans formulated to achieve the specific goals of the optimization strategy, which covers the specific operations of each link from project analysis, design adjustment to code implementation; the adjusted project code refers to the code set obtained after modifying, adjusting and improving the original code of the front-end project according to the implementation steps. This code set has undergone preliminary optimization processing, including optimization of code structure, improvement of algorithm, rewriting of function, etc.; the performance optimization point refers to those parts or factors in the adjusted project code that play a key role in improving the performance of the project, which can be a specific module, function, algorithm in the code, or a link or configuration in the project architecture.

[0076] Furthermore, the determination of the specific goals corresponding to the optimization strategy can be achieved through a goal management tool, such as: using tools such as Trello to create project goal cards, breaking down the optimization strategy into specific goals, and clarifying the person in charge, time nodes and expected results of each goal; the query of the implementation steps corresponding to the specific goals can be achieved through an association rule mining algorithm, such as: an association rule mining algorithm can be used to mine the association between goals and implementation steps; the code adjustment of the front-end project can be achieved through a code analysis tool, such as: ESLint and other tools; the extraction of performance optimization points in the adjusted project code can be achieved through a performance analysis tool, such as: analyzing the performance during page loading and running, including CPU usage, memory usage, function execution time, etc., so as to extract the corresponding performance optimization points; the optimization processing of the front-end project can be achieved through a reinforcement learning algorithm, such as: during the optimization process, a reinforcement learning algorithm can be used to automatically adjust the optimization strategy according to user behavior and performance data.

[0077] By analyzing the project objectives corresponding to the optimization project, the present invention can clearly understand the final results to be achieved by the optimization project, accurately judge whether the project has met the expected requirements, and summarize the successful experiences and lessons learned in the process of achieving the goals, which is helpful to formulate more reasonable and feasible goals and optimization strategies in subsequent projects.

[0078] Among them, the project goal refers to the specific, measurable and clearly directional results or states expected to be achieved in the front-end project optimization process, which covers multiple aspects, including but not limited to performance improvement goals, such as shortening page loading time to within a specific number of seconds, improving system response speed to meet users' real-time interaction needs, etc.; user experience improvement goals, such as optimizing interface design to enhance the convenience and comfort of user operations, improving the readability and attractiveness of content to increase user stay time and participation, etc.; functional improvement goals, such as adding specific functional modules to meet business development needs, improving the stability and reliability of existing functions to reduce the error rate during user use, etc.; and technical optimization goals, such as adopting new front-end technology frameworks or tools to improve development efficiency and code quality, optimizing project architecture to enhance system maintainability and scalability, etc. Optionally, the analysis of the project goals corresponding to the optimization project can be achieved through the goal decomposition method, such as: decomposing the overall goals of the optimization project according to dimensions such as function, performance, and user experience.

[0079] Furthermore, the present invention generates a front-end management plan corresponding to the front-end project based on the project goals, which can ensure that the development and operation of the front-end project are closely centered around a clear direction. By breaking down the project goals into specific management strategies and action plans, team members have clear guidance during the work process, avoiding blindness and arbitrariness, thereby improving work efficiency and quality.

[0080] Among them, the front-end management plan refers to a comprehensive, systematic and targeted management plan and strategy set formulated to ensure that the front-end project can successfully achieve the predetermined project goals. It covers all aspects of the front-end project development and operation and maintenance process, including but not limited to project organization and team management, technology selection and architecture planning, development process and progress control, quality assurance and testing strategy, resource allocation and risk management, user experience design and optimization, performance monitoring and optimization, and collaborative communication mechanisms with other relevant departments or teams. Optionally, the generation of the front-end management plan corresponding to the front-end project can be achieved through a plan generation tool, such as: Project, Trello and other tools.

[0081] It should be understood that the order of execution of the steps in the above embodiment does not necessarily mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present invention.

[0082] In one embodiment, a device for implementing front-end management based on a code repository is provided, and the device for implementing front-end management based on a code repository corresponds one-to-one to the method for implementing front-end management based on a code repository in the above embodiment. Figure 3 As shown, the device for implementing front-end management based on code repository includes a content combing module 201, a version control module 202, an effect evaluation module 203, a strategy formulation module 204 and a solution generation module 205. The detailed description of each functional module is as follows:

[0083] The content combing module 201 is used to obtain the development scenario corresponding to the front-end project, analyze the public content requirements in the development scenario, determine the public content category in the development scenario based on the public content requirements, comb the content of the public content category, and obtain a public content list;

[0084] A version control module 202 is used to build a dual warehouse management mechanism corresponding to the front-end project based on the public content list, and perform version control on the public content in the public warehouse of the dual warehouse management mechanism to obtain version control information;

[0085] Effect evaluation module 203, used to analyze the development efficiency and code quality corresponding to the front-end project based on the dual warehouse management mechanism and version control information, calculate the overall performance index corresponding to the front-end project according to the development efficiency and the code quality, and evaluate the development effect corresponding to the front-end project based on the overall performance index;

[0086] A strategy formulation module 204, for identifying positive factors and negative factors in the development effect, analyzing the project architecture corresponding to the front-end project based on the positive factors and the negative factors, and formulating an optimization strategy for the front-end project based on the project architecture;

[0087] The solution generation module 205 is used to optimize the front-end project based on the optimization strategy to obtain the optimized project, analyze the project goal corresponding to the optimized project, and generate a front-end management solution corresponding to the front-end project based on the project goal.

[0088] For the specific definition of the device for implementing front-end management based on the code warehouse, please refer to the definition of the method for front-end management above, which will not be repeated here. Each module in the above-mentioned device for implementing front-end management based on the code warehouse can be implemented in whole or in part by software, hardware and a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

[0089] In one embodiment, when the content combing module 201 performs content combing on the public content category to obtain a public content list, it is used to: analyze the functional attributes corresponding to the public content category to determine the content combing rules corresponding to the functional attributes; based on the content combing rules, screen the specific content elements corresponding to the public content category; classify the similar content items corresponding to the specific content elements; and based on the similar content items, generate a public content list corresponding to the public content category.

[0090] In one embodiment, when the version control module 202 performs version control on the public content in the public warehouse and obtains version control information, it is used to: analyze the public content structure in the public warehouse; determine the version control strategy corresponding to the public content structure; create a version control environment corresponding to the public warehouse based on the version control strategy; collect version control data in the version control environment; mark the version number and key points corresponding to the version control data; and perform version control on the public content in the public warehouse based on the version number and the key points to obtain version control information.

[0091] In one embodiment, when the effect evaluation module 203 is executed and based on the overall performance indicator, evaluates the development effect corresponding to the front-end project, it is used to: analyze the constituent dimensions corresponding to the overall performance indicator; determine the evaluation criteria corresponding to the constituent dimensions; based on the evaluation criteria, quantitatively score the overall performance indicator to obtain a scoring result; screen the key scoring points in the scoring result; and based on the key scoring points, evaluate the development effect corresponding to the front-end project.

[0092] In one embodiment, when analyzing the project architecture corresponding to the front-end project based on the positive factors and the negative factors, the strategy formulation module 204 is used to: analyze the factor influence points corresponding to the positive factors and the negative factors; determine the factor analysis direction corresponding to the factor influence points; based on the factor analysis direction, perform a preliminary analysis on the front-end project to obtain preliminary analysis results; screen key architecture features in the preliminary analysis results; and analyze the project architecture corresponding to the front-end project based on the key architecture features.

[0093] In one embodiment, when the strategy formulation module 204 is executing to formulate the optimization strategy for the front-end project based on the project architecture, it is used to: query the current status corresponding to the project architecture; analyze the optimization direction corresponding to the current status; based on the optimization direction, collect the project key points corresponding to the front-end project; based on the project key points, formulate the optimization strategy for the front-end project.

[0094] In one embodiment, when the solution generation module 205 performs optimization processing on the front-end project based on the optimization strategy to obtain the optimized project, it is used to: determine the specific goal corresponding to the optimization strategy; query the implementation steps corresponding to the specific goal; based on the implementation steps, perform code adjustment on the front-end project to obtain an adjustment project code; extract performance optimization points in the adjustment project code; based on the performance optimization points, optimize the front-end project to obtain the optimized project.

[0095] For the specific limitations of the device for implementing front-end management based on the code warehouse, please refer to the limitations of the method for implementing front-end management based on the code warehouse above, which will not be repeated here. Each module in the above-mentioned device for implementing front-end management based on the code warehouse can be implemented in whole or in part by software, hardware and a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

[0096] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 4As shown. The computer device includes a processor, a memory, a network interface and a database connected via a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile and / or volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external client via a network connection. When the computer program is executed by the processor, it implements the functions or steps of a method for implementing front-end management based on a code repository on the service side.

[0097] In one embodiment, a computer device is provided. The computer device may be a client, and its internal structure diagram may be as follows: Figure 5 As shown. The computer device includes a processor, a memory, a network interface, a display screen and an input device connected via a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external server via a network connection. When the computer program is executed by the processor, it implements the functions or steps of the client side of a method for implementing front-end management based on a code repository

[0098] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the following steps when executing the computer program:

[0099] Obtaining a development scenario corresponding to a front-end project, analyzing public content requirements in the development scenario, determining public content categories in the development scenario based on the public content requirements, sorting out the public content categories, and obtaining a public content list;

[0100] Based on the public content list, a dual warehouse management mechanism corresponding to the front-end project is constructed, and version control is performed on the public content in the public warehouse of the dual warehouse management mechanism to obtain version control information;

[0101] Based on the dual warehouse management mechanism and version control information, the development efficiency and code quality corresponding to the front-end project are analyzed, and according to the development efficiency and the code quality, the overall performance index corresponding to the front-end project is calculated, and based on the overall performance index, the development effect corresponding to the front-end project is evaluated;

[0102] Identify positive factors and negative factors in the development effect, analyze the project architecture corresponding to the front-end project based on the positive factors and the negative factors, and formulate an optimization strategy for the front-end project based on the project architecture;

[0103] Based on the optimization strategy, the front-end project is optimized to obtain an optimized project, the project goal corresponding to the optimized project is analyzed, and based on the project goal, a front-end management plan corresponding to the front-end project is generated.

[0104] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0105] Obtaining a development scenario corresponding to a front-end project, analyzing public content requirements in the development scenario, determining public content categories in the development scenario based on the public content requirements, sorting out the public content categories, and obtaining a public content list;

[0106] Based on the public content list, a dual warehouse management mechanism corresponding to the front-end project is constructed, and version control is performed on the public content in the public warehouse of the dual warehouse management mechanism to obtain version control information;

[0107] Based on the dual warehouse management mechanism and version control information, the development efficiency and code quality corresponding to the front-end project are analyzed, and according to the development efficiency and the code quality, the overall performance index corresponding to the front-end project is calculated, and based on the overall performance index, the development effect corresponding to the front-end project is evaluated;

[0108] Identify positive factors and negative factors in the development effect, analyze the project architecture corresponding to the front-end project based on the positive factors and the negative factors, and formulate an optimization strategy for the front-end project based on the project architecture;

[0109] Based on the optimization strategy, the front-end project is optimized to obtain an optimized project, the project goal corresponding to the optimized project is analyzed, and based on the project goal, a front-end management plan corresponding to the front-end project is generated.

[0110] It should be noted that the above functions or steps that can be implemented by the computer-readable storage medium or computer device can refer to the relevant descriptions on the server side and the client side in the aforementioned method embodiment. To avoid repetition, they will not be described one by one here.

[0111] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0112] Those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example. In actual applications, the above-mentioned functions can be distributed and completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.

[0113] The above-described embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit them; although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some of the technical features therein by equivalents; and these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the various embodiments of the present invention, and should be included in the protection scope of the present invention. It should be noted that if software tools or components other than those of the company appear in the embodiments of this application, they are only used for illustration and do not represent actual use.

Claims

1. A method for implementing front-end management based on a code repository, characterized in that: include: Obtaining a development scenario corresponding to a front-end project, analyzing public content requirements in the development scenario, determining public content categories in the development scenario based on the public content requirements, sorting out the public content categories, and obtaining a public content list; Based on the public content list, a dual warehouse management mechanism corresponding to the front-end project is constructed, and version control is performed on the public content in the public warehouse of the dual warehouse management mechanism to obtain version control information; Based on the dual warehouse management mechanism and version control information, the development efficiency and code quality corresponding to the front-end project are analyzed, and according to the development efficiency and the code quality, the overall performance index corresponding to the front-end project is calculated, and based on the overall performance index, the development effect corresponding to the front-end project is evaluated; Identify positive factors and negative factors in the development effect, analyze the project architecture corresponding to the front-end project based on the positive factors and the negative factors, and formulate an optimization strategy for the front-end project based on the project architecture; Based on the optimization strategy, the front-end project is optimized to obtain an optimized project, the project goal corresponding to the optimized project is analyzed, and based on the project goal, a front-end management plan corresponding to the front-end project is generated.

2. The method for implementing front-end management based on a code repository according to claim 1, characterized in that: The public content category is sorted to obtain a public content list, including: Analyzing functional attributes corresponding to the public content category; Determine content combing rules corresponding to the functional attributes; Based on the content combing rule, screening specific content elements corresponding to the public content category; Classifying similar content items corresponding to the specific content elements; Based on the classified similar content items, a public content list corresponding to the public content category is generated.

3. The method for implementing front-end management based on a code repository according to claim 1, characterized in that: The performing version control on the public content in the public warehouse of the dual warehouse management mechanism to obtain version control information includes: Analyzing the public content structure in the public warehouse of the dual warehouse management mechanism; Determining a version control strategy corresponding to the common content structure; Based on the version control strategy, create a version control environment corresponding to the public warehouse; Collecting version control data in the version control environment; Marking the version number and key points corresponding to the version control data; Based on the version number and the key point, version control is performed on the public content in the public repository to obtain version control information.

4. The method for implementing front-end management based on a code repository according to claim 1, characterized in that: The evaluating the development effect corresponding to the front-end project based on the overall performance indicator includes: Analyze the component dimensions corresponding to the overall performance indicators; Determining evaluation criteria corresponding to the constituent dimensions; Based on the evaluation criteria, the overall performance index is quantitatively scored to obtain a scoring result; Filtering key scoring points in the scoring results; Based on the key scoring points, the development effect corresponding to the front-end project is evaluated.

5. The method for implementing front-end management based on a code repository according to claim 1, characterized in that: The analyzing the project architecture corresponding to the front-end project based on the positive factors and the negative factors includes: Analyze the factor influence points corresponding to the positive factors and negative factors; Determine the factor analysis direction corresponding to the factor influence point; Based on the factor analysis direction, a preliminary analysis is performed on the front-end project to obtain preliminary analysis results; Screening key architectural features from the preliminary analysis results; Based on the key architecture features, the project architecture corresponding to the front-end project is analyzed.

6. The method for implementing front-end management based on a code repository according to claim 1, characterized in that: Formulating an optimization strategy for the front-end project based on the project architecture includes: Query the current status corresponding to the project architecture; Analyze the optimization direction corresponding to the current state; Based on the optimization direction, collecting project key points corresponding to the front-end project; Based on the project highlights, an optimization strategy for the front-end project is formulated.

7. The method for implementing front-end management based on a code repository according to claim 1, characterized in that: The front-end project is optimized based on the optimization strategy to obtain an optimized project, including: Determine the specific goal corresponding to the optimization strategy; Query the implementation steps corresponding to the specific goals; Based on the implementation steps, the front-end project is code-adjusted to obtain an adjusted project code; Extracting performance optimization points in the adjustment item code; Based on the performance optimization point, the front-end project is optimized to obtain an optimized project.

8. A device for implementing front-end management based on a code repository, characterized in that: include: A content combing module is used to obtain the development scenario corresponding to the front-end project, analyze the public content requirements in the development scenario, determine the public content category in the development scenario based on the public content requirements, comb the content of the public content category, and obtain a public content list; A version control module, used to build a dual warehouse management mechanism corresponding to the front-end project based on the public content list, and perform version control on the public content in the public warehouse of the dual warehouse management mechanism to obtain version control information; An effect evaluation module, used to analyze the development efficiency and code quality corresponding to the front-end project based on the dual warehouse management mechanism and version control information, calculate the overall performance index corresponding to the front-end project according to the development efficiency and the code quality, and evaluate the development effect corresponding to the front-end project based on the overall performance index; A strategy formulation module, used to identify positive factors and negative factors in the development effect, analyze the project architecture corresponding to the front-end project based on the positive factors and the negative factors, and formulate an optimization strategy for the front-end project based on the project architecture; The solution generation module is used to optimize the front-end project based on the optimization strategy to obtain the optimized project, analyze the project goals corresponding to the optimized project, and generate a front-end management solution corresponding to the front-end project based on the project goals.

9. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the method for implementing front-end management based on a code repository as described in any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the method for implementing front-end management based on a code repository as described in any one of claims 1 to 7 is implemented.

Images