CN116880898A

CN116880898A - Document processing method and device, readable medium and electronic equipment

Info

Publication number: CN116880898A
Application number: CN202310836328.6A
Authority: CN
Inventors: 包宏权; 涂兆峰; 王昱林; 何鸣明
Original assignee: Beijing Youzhuju Network Technology Co Ltd
Current assignee: Beijing Youzhuju Network Technology Co Ltd
Priority date: 2023-07-07
Filing date: 2023-07-07
Publication date: 2023-10-13

Abstract

The embodiment of the disclosure relates to a document processing method, a document processing device, a readable medium and electronic equipment. The method comprises the following steps: and acquiring an interface document corresponding to the target interface, responding to the received information adjustment instruction, and updating the interface document and the interface configuration data according to the information adjustment instruction. The interface document is a document generated according to the interface configuration data. Therefore, the interface document can be automatically generated, the interface document and the interface configuration data can be automatically and synchronously updated according to the information adjustment instruction, the consistency of the interface document and the interface configuration data is realized, and the updating efficiency and the updating reliability of the interface document are improved.

Description

Document processing method and device, readable medium and electronic equipment

Technical Field

The disclosure relates to the technical field of computers, and in particular relates to a document processing method, a document processing device, a readable medium and electronic equipment.

Background

With the development of computer technology, an application program of a service platform can provide more and more functions for a user, the application program can be opened to the user for use through an application program interface (Application Programming Interface, API), the user can call the functions provided by the application program through the API without considering bottom source codes, and the requirements of the user are met.

To facilitate the user's use of the API, the user may be provided with an interface document, such as an API document, through which the user may obtain the functionality and method of use of the API. In the related art, the cost of manually generating API documents is high and the efficiency is low.

Disclosure of Invention

This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

According to a first aspect of embodiments of the present disclosure, there is provided a document processing method, the method including:

acquiring an interface document corresponding to a target interface; the interface document is a document generated according to interface configuration data;

and in response to receiving an information adjustment instruction, updating the interface document and the interface configuration data according to the information adjustment instruction.

According to one or more embodiments of the present disclosure, the interface configuration data includes first information corresponding to the target interface, where the first information is editable information; the updating the interface document and the interface configuration data according to the information adjustment instruction includes:

updating the first information according to the information adjustment instruction;

and updating the interface document and the interface configuration data according to the updated first information.

According to one or more embodiments of the present disclosure, the first information includes at least one of:

descriptive information of the target interface;

and the interface parameters of the target interface comprise at least one of head parameters, request parameters and response parameters.

According to one or more embodiments of the present disclosure, the method further comprises:

and in response to receiving a parameter adjustment instruction, adding or deleting the interface parameters displayed in the interface document according to the parameter adjustment instruction, wherein the interface parameters displayed in the interface document are a subset or a whole set of the interface parameters contained in the interface configuration data.

and under the condition that the interface configuration data is changed, updating the interface document according to the changed interface configuration data.

displaying the updated interface document and the updated difference information of the interface document; wherein the updated difference information includes differences between the updated interface document and the interface document before the update;

receiving an audit instruction;

and under the condition that the auditing instruction passes the auditing, issuing an updated interface document.

According to one or more embodiments of the present disclosure, the interface configuration data further includes second information corresponding to the target interface, where the second information is non-editable information.

According to one or more embodiments of the present disclosure, the second information includes at least one of: interface name, request address, request mode, request instance, reply instance, error code.

According to one or more embodiments of the present disclosure, the obtaining the interface document corresponding to the target interface includes:

determining the target interface;

and generating the interface document corresponding to the target interface according to the interface configuration data.

According to a second aspect of embodiments of the present disclosure, there is provided a document processing apparatus, the apparatus comprising:

the acquisition module is used for acquiring an interface document corresponding to the target interface; the interface document is a document generated according to interface configuration data;

and the updating module is used for responding to the received information adjustment instruction and updating the interface document and the interface configuration data according to the information adjustment instruction.

According to a third aspect of embodiments of the present disclosure, there is provided a computer readable medium having stored thereon a computer program which, when executed by a processing device, implements the steps of the method of the first aspect of the present disclosure.

According to a fourth aspect of embodiments of the present disclosure, there is provided an electronic device, comprising:

a storage device having a computer program stored thereon;

processing means for executing said computer program in said storage means to carry out the steps of the method of the first aspect of the disclosure.

By adopting the technical scheme, the interface document corresponding to the target interface is acquired, the information adjustment instruction is received, and the interface document and the interface configuration data are updated according to the information adjustment instruction. The interface document is a document generated according to the interface configuration data. Therefore, the interface document can be automatically generated, the interface document and the interface configuration data can be automatically and synchronously updated according to the information adjustment instruction, the consistency of the interface document and the interface configuration data is realized, and the updating efficiency and the updating reliability of the interface document are improved.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The above and other features, advantages, and aspects of embodiments of the present disclosure will become more apparent by reference to the following detailed description when taken in conjunction with the accompanying drawings. The same or similar reference numbers will be used throughout the drawings to refer to the same or like elements. It should be understood that the figures are schematic and that elements and components are not necessarily drawn to scale. In the drawings:

FIG. 1 is a flow chart illustrating a method of document processing according to an embodiment of the present disclosure.

FIG. 2 is a flow chart illustrating another document processing method according to an embodiment of the present disclosure.

FIG. 3 is a flow chart illustrating another document processing method according to an embodiment of the present disclosure.

FIG. 4 is a flow chart illustrating yet another document processing method according to an embodiment of the present disclosure.

Fig. 5 is a block diagram of a document processing apparatus according to an embodiment of the present disclosure.

Fig. 6 is a block diagram of a document processing apparatus according to an embodiment of the present disclosure.

Fig. 7 is a block diagram of an electronic device, shown in accordance with an embodiment of the present disclosure.

Detailed Description

Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure have been shown in the accompanying drawings, it is to be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for illustration purposes only and are not intended to limit the scope of the present disclosure.

It should be understood that the various steps recited in the method embodiments of the present disclosure may be performed in a different order and/or performed in parallel. Furthermore, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present disclosure is not limited in this respect.

The term "comprising" and variations thereof as used in this disclosure are open ended terms that include, but are not limited to. The term "based on" is based at least in part on. The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments. Related definitions of other terms will be given in the description below.

It should be noted that the terms "first," "second," and the like in this disclosure are merely used to distinguish between different devices, modules, or units and are not used to define an order or interdependence of functions performed by the devices, modules, or units.

It should be noted that references to "one", "a plurality" and "a plurality" in this disclosure are intended to be illustrative rather than limiting, and those of ordinary skill in the art will appreciate that "one or more" is intended to be understood as "one or more" unless the context clearly indicates otherwise. In the description of the present disclosure, unless otherwise indicated, "a plurality" means two or more than two, and other adjectives are similar thereto; "at least one item", "an item" or "a plurality of items" or the like, refer to any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (a) may represent any number a; as another example, one (or more) of a, b, and c may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or plural; "and/or" is an association relationship describing an association object, meaning that there may be three relationships, e.g., a and/or B, which may represent: there are three cases, a alone, a and B together, and B alone, wherein a, B may be singular or plural. The character "/" indicates that the front-rear association object is an or relationship. The singular forms "a", "an", "the" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.

Although operations or steps are described in a particular order in the figures in the disclosed embodiments, it should not be understood as requiring that such operations or steps be performed in the particular order shown or in sequential order, or that all illustrated operations or steps be performed, to achieve desirable results. In embodiments of the present disclosure, these operations or steps may be performed serially; these operations or steps may also be performed in parallel; some of these operations or steps may also be performed.

The names of messages or information interacted between the various devices in the embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

It will be appreciated that prior to using the technical solutions disclosed in the embodiments of the present disclosure, the user should be informed and authorized of the type, usage range, usage scenario, etc. of the personal information related to the present disclosure in an appropriate manner according to the relevant legal regulations.

For example, in response to receiving an active request from a user, a prompt is sent to the user to explicitly prompt the user that the operation it is requesting to perform will require personal information to be obtained and used with the user. Thus, the user can autonomously select whether to provide personal information to software or hardware such as an electronic device, an application program, a server or a storage medium for executing the operation of the technical scheme of the present disclosure according to the prompt information.

As an alternative but non-limiting implementation, in response to receiving an active request from a user, the manner in which the prompt information is sent to the user may be, for example, a popup, in which the prompt information may be presented in a text manner. In addition, a selection control for the user to select to provide personal information to the electronic device in a 'consent' or 'disagreement' manner can be carried in the popup window.

It will be appreciated that the above-described notification and user authorization process is merely illustrative and not limiting of the implementations of the present disclosure, and that other ways of satisfying relevant legal regulations may be applied to the implementations of the present disclosure.

Meanwhile, it can be understood that the data (including but not limited to the data itself, the acquisition or the use of the data) related to the technical scheme should conform to the requirements of the corresponding laws and regulations and related regulations.

First, an application scenario of the present disclosure will be described. The present disclosure may be applied to document processing scenarios, particularly processing scenarios of interface documents or API documents.

An API, i.e. an application program interface, provides a more underlying atomization capability than a commonly operated visualization platform (e.g. advertising platform, etc.), just like a building block. The clients can start from the self service scene, build the self service management platform through the API, process more customized demands, bring more expansion space for the service, and the API is applied to the advertisement putting platform, so that the advertisement putting efficiency can be improved. In order to facilitate the user to use the API, the user can be provided with an API document, and the user can acquire the function and the using method of the API through the API document and complete access by reading the API document. Thus, the accuracy and timeliness of the API documents is of paramount importance.

In the related art, the API interface is changed more frequently, and the cost of manually generating the API document is high and the efficiency is low. Illustratively, a platform currently opens a 500+ interface to the outside, involving 50+ interface changes weekly. Frequent interface changes simply depend on manpower to update the document, and the document is inefficient, untimely and inconsistent with the interface capability.

In order to solve the problems, the disclosure provides a document processing method, a document processing device, a readable medium and an electronic device.

The present disclosure is described below in connection with specific embodiments.

FIG. 1 is a flow chart illustrating a method of document processing according to an embodiment of the present disclosure. The method may be applied to an electronic device, which may include a terminal device, such as a smart phone, smart wearable device, smart speaker, smart tablet, PDA (Personal Digital Assistant ), CPE (Customer Premise Equipment, customer terminal device), personal computer, vehicle terminal, etc.; the electronic device may also include a server, such as a local server or cloud server. As shown in fig. 1, the method may include:

s101, acquiring an interface document corresponding to a target interface.

The interface document is a document generated according to the interface configuration data.

In some embodiments, the interface configuration data may be an interface swagger profile, and the interface document may be generated by parsing the swagger.

In some embodiments, the step S101 may include the sub-steps of:

first, a target interface is determined.

Then, according to the interface configuration data, an interface document corresponding to the target interface is generated.

For example, an interface selection instruction input by the first user may be received, where the interface selection instruction may include a target interface of the interface document that the first user needs to generate. In this way, the target interface that needs to generate the interface document can be determined based on the user's selection. The first user may be a user who generates or publishes an interface document, for example, an operator or document manager of API software.

In some embodiments, the interface configuration data may be data stored in a server, which may be data for storing API software and/or API software configuration. The interface configuration data may be generated and/or updated by a developer of the API software, e.g., the developer may generate the interface configuration data from one or more APIs during development of the API software, and may update the interface configuration data synchronously as the API software is updated.

According to the interface configuration data, an interface document corresponding to the target interface can be automatically generated.

S102, in response to receiving the information adjustment instruction, updating the interface document and the interface configuration data according to the information adjustment instruction.

The information adjustment instruction can be used for adjusting information in the generated interface document and synchronously updating the interface document and the interface configuration data according to the adjusted information.

In some embodiments, the interface configuration data may include first information corresponding to the target interface, where the first information is editable information. The step S102 may include the following substeps:

first, the first information is updated according to the information adjustment instruction.

And secondly, updating the interface document and the interface configuration data according to the updated first information.

In one implementation, the first information may include at least one of:

descriptive information of the target interface;

One or more fields may be included in each interface parameter. Illustratively, one interface parameter includes a field list structure as shown in table 1 below:

field English name	Data type	Field chinese name
			name	string	Field name
type	string	Field type
			description	string	Description information
label	string	Label (Label)
			disabled	boolean	Whether or not to hide from outside
children	object	Sub-level parameters

TABLE 1

As shown in table 1, each interface parameter may include at least one of the six fields described above, including: the name (field name) data type is string (character string) format, the type (field type) data type is string, the description (description information) data type is string, the label (tag) data type is string, the disable (whether hidden from the outside) data type is boolean, and the child parameter data type is object. Wherein label can be used to characterize whether the field interface parameters have to be filled or whether the conditions have to be filled.

In other embodiments, the interface configuration data may include second information corresponding to the target interface, where the second information is non-editable information.

In one implementation, the second information may include at least one of: interface name, request address, request mode, request instance, reply instance, error code.

In another implementation, the second information may further include information of a field name, a field type, etc. of an interface parameter of the target interface.

In other embodiments, the interface configuration data may include the first information and the second information described above.

The interface configuration data may include, for example, an interface name, an interface description, a request address, a request manner, a header parameter, a request parameter, a response parameter, a request instance, a response instance, an error code.

By adopting the method, the interface document corresponding to the target interface is acquired, the information adjustment instruction is received, and the interface document and the interface configuration data are updated according to the information adjustment instruction. The interface document is a document generated according to the interface configuration data. Therefore, the interface document can be automatically generated, the interface document and the interface configuration data can be automatically and synchronously updated according to the information adjustment instruction, the consistency of the interface document and the interface configuration data is realized, and the updating efficiency and the updating reliability of the interface document are improved.

FIG. 2 is a flow chart illustrating another document processing method according to an embodiment of the present disclosure. As shown in fig. 2, the method may include:

s101, acquiring an interface document corresponding to a target interface.

S202, in response to receiving the parameter adjustment instruction, adding or deleting the interface parameters displayed in the interface document according to the parameter adjustment instruction.

The interface parameters displayed in the interface document are subsets or whole sets of the interface parameters contained in the interface configuration data.

The parameter adjustment instruction may be an instruction input by the first user through the control interface, and the parameter adjustment instruction may be used to add or delete an interface parameter shown in the interface document.

In some embodiments, the interface document obtained in the step S101 may include a complete set of interface parameters in the interface configuration data, that is, the interface parameters included in the interface document may be the same as the interface parameters included in the interface configuration data; the user may input a parameter adjustment instruction to decrease the interface parameters contained in the interface document, and after decreasing the interface parameters, the user may also input a new parameter adjustment instruction to increase the interface parameters contained in the interface document.

For example, the interface configuration data includes 10 interface parameters, where 3 interface parameters may be default values and no modification is required, at this time, the first user may input a parameter adjustment instruction, delete the 3 interface parameters, and only display or include another 7 interface parameters in the interface document.

Therefore, the interface parameters displayed in the interface document can be added or deleted according to the parameter adjustment instruction, so that the interface document can be adjusted more flexibly, and the usability of the interface document is improved.

FIG. 3 is a flow chart illustrating another document processing method according to an embodiment of the present disclosure. As shown in fig. 3, the method may include:

s101, acquiring an interface document corresponding to a target interface.

S302, adjusting the content of the interface document.

In some embodiments, the interface document and the interface configuration data may be updated in response to receiving the information adjustment instruction according to the information adjustment instruction.

It should be noted that, for the specific manner of updating the interface document and the interface configuration data and the information adjustment instruction, reference may be made to the description of step S102 in the foregoing embodiments of the present disclosure, which is not repeated here.

In other embodiments, the interface parameters presented in the interface document may be added or deleted in response to receiving the parameter adjustment instructions in accordance with the parameter adjustment instructions.

It should be noted that, for the specific manner of adding or deleting the parameter adjustment instruction and the interface parameter shown in the interface document, reference may be made to the description of step S202 in the foregoing embodiment of the disclosure, which is not repeated herein.

S303, auditing and publishing the adjusted interface document.

In some embodiments, the adjusted interface document may be presented, an audit instruction is received, and if the audit instruction is an audit pass, the adjusted interface document is issued.

For example, the adjusted interface document may be presented to the second user and an audit instruction sent by the second user may be received. The second user may be a user who reviews the interface document. The second user may be different from the first user or the same.

It should be noted that, the auditing and publishing in the steps S302 and S303 are optional steps. For example, the interface document can be directly issued to the user for use without adjustment or auditing. For another example, the interface document can be directly issued to the user for use after adjustment. For another example, the interface document may be released to the user for use after auditing without adjustment.

Therefore, the interface document can be adjusted, audited and released through the steps, the interface document can be flexibly adjusted, and the quality of the interface document is improved through the audited, so that the accuracy and usability of the interface document can be improved.

FIG. 4 is a flow chart illustrating yet another document processing method according to an embodiment of the present disclosure. As shown in fig. 4, the method may include:

s101, acquiring an interface document corresponding to a target interface.

S402, when the interface configuration data is changed, updating the interface document according to the changed interface configuration data.

In some embodiments, content related to the target interface in the interface configuration data may be monitored, and in the case that the content is written to change, the changed interface configuration data may be acquired, and the interface document may be updated.

In other embodiments, the electronic device may receive an interface online update indication sent by the server, where the interface online update indication may be used to indicate that the interface configuration data has been changed. Whether the fields of the interface parameters contained in the interface document are updated or not can be determined according to the online update instruction of the interface, if the interface fields are updated, the changed interface configuration data can be obtained, and the interface document is updated according to the changed interface configuration data.

In one implementation, if the interface field is updated, the latest interface parameters (e.g., header parameters, request parameters, response parameters) and interface examples (e.g., request examples, response examples) can be obtained through the lark notification and document detail notification changes, and the interface document is updated according to the interface parameters and interface examples.

S403, auditing and publishing the updated interface document.

In some embodiments, updated information may be presented, an audit instruction is received, and if the audit instruction is an audit pass, an updated interface document is issued.

Wherein the update information may include at least one of: updated interface document, updated difference information of the interface document. Wherein the updated difference information may include differences between the updated interface document and the pre-updated interface document.

For example, the content of the update of the interface document at this time may be presented in the form of a revision schema.

For another example, the updated difference information of the interface document may be presented in a list.

The updated content of the interface document can be intuitively and clearly displayed through the updated difference information, so that a user can conveniently check and determine whether the updated content accords with expectations.

In some embodiments, an updated interface document may be presented, along with updated difference information for the interface document.

In other embodiments, only updated interface documents may be presented; alternatively, only updated difference information for the interface document may be presented.

In some embodiments, the updated information may be presented to the second user and an audit instruction sent by the second user may be received. The second user may be a user who reviews the interface document. The second user may be different from the first user or the same.

In this way, when the interface configuration data is changed, the interface document is updated according to the changed interface configuration data, so that the interface document can be automatically updated, and the usability of the interface document is ensured.

Fig. 5 is a block diagram of a document processing apparatus 1100, shown in accordance with an embodiment of the present disclosure. As shown in fig. 5, the apparatus 1100 may include:

an obtaining module 1101, configured to obtain an interface document corresponding to a target interface; the interface document is a document generated according to interface configuration data;

and the updating module 1102 is configured to update the interface document and the interface configuration data according to the information adjustment instruction in response to receiving the information adjustment instruction.

According to one or more embodiments of the present disclosure, the interface configuration data includes first information corresponding to the target interface, where the first information is editable information; the updating module 1102 is configured to update the first information according to the information adjustment instruction; and updating the interface document and the interface configuration data according to the updated first information.

descriptive information of the target interface;

According to one or more embodiments of the present disclosure, the updating module 1102 is further configured to, in response to receiving a parameter adjustment instruction, add or delete an interface parameter shown in the interface document according to the parameter adjustment instruction, where the interface parameter shown in the interface document is a subset or a complete set of interface parameters included in the interface configuration data.

In accordance with one or more embodiments of the present disclosure, the updating module 1102 is further configured to, in a case where the interface configuration data is changed, update the interface document according to the changed interface configuration data.

Fig. 6 is a block diagram of a document processing apparatus 1100, shown in accordance with an embodiment of the present disclosure. As shown in fig. 6, the apparatus 1100 may further include:

the display module 1103 is configured to display the updated interface document and updated difference information of the interface document; wherein the updated difference information includes differences between the updated interface document and the interface document before the update;

an audit module 1104 for receiving audit instructions; and under the condition that the auditing instruction passes the auditing, issuing an updated interface document.

In accordance with one or more embodiments of the present disclosure, the obtaining module 1101 is configured to determine the target interface; and generating the interface document corresponding to the target interface according to the interface configuration data.

The specific manner in which the various modules perform the operations in the apparatus of the above embodiments have been described in detail in connection with the embodiments of the method, and will not be described in detail herein.

Referring now to fig. 7, a schematic diagram of an electronic device 2000 (e.g., a terminal device or server) suitable for use in implementing embodiments of the present disclosure is shown. The terminal devices in the embodiments of the present disclosure may include, but are not limited to, mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and the like, and stationary terminals such as digital TVs, desktop computers, and the like. Servers in embodiments of the present disclosure may include, but are not limited to, such as local servers, cloud servers, individual servers, distributed servers, and the like. The electronic device shown in fig. 7 is merely an example and should not be construed to limit the functionality and scope of use of the disclosed embodiments.

As shown in fig. 7, the electronic device 2000 may include a processing apparatus (e.g., a central processing unit, a graphics processor, etc.) 2001, which may perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 2002 or a program loaded from a storage apparatus 2008 into a Random Access Memory (RAM) 2003. In the RAM2003, various programs and data required for the operation of the electronic device 2000 are also stored. The processing device 2001, ROM2002, and RAM2003 are connected to each other by a bus 2004. An input/output (I/O) interface 2005 is also connected to bus 2004.

In general, the following devices may be connected to the input/output interface 2005: input devices 2006 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, and the like; output devices 2007 including, for example, a Liquid Crystal Display (LCD), speakers, vibrators, and the like; storage 2008 including, for example, a magnetic tape, a hard disk, and the like; and a communication device 2009. The communication means 2009 may allow the electronic device 2000 to communicate with other devices wirelessly or by wire to exchange data. While fig. 7 shows an electronic device 2000 having various means, it is to be understood that not all of the illustrated means are required to be implemented or provided. More or fewer devices may be implemented or provided instead.

In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a non-transitory computer readable medium, the computer program comprising program code for performing the method shown in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication device 2009, or installed from the storage device 2008, or installed from the ROM 2002. The above-described functions defined in the method of the embodiment of the present disclosure are performed when the computer program is executed by the processing device 2001.

It should be noted that the computer readable medium described in the present disclosure may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this disclosure, a computer-readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present disclosure, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, fiber optic cables, RF (radio frequency), and the like, or any suitable combination of the foregoing.

In some implementations, the clients, servers may communicate using any currently known or future developed network protocol, such as HTTP (HyperText Transfer Protocol ), and may be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), the internet (e.g., the internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed networks.

The computer readable medium may be contained in the electronic device; or may exist alone without being incorporated into the electronic device.

The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: acquiring an interface document corresponding to a target interface; the interface document is a document generated according to interface configuration data; and in response to receiving an information adjustment instruction, updating the interface document and the interface configuration data according to the information adjustment instruction.

Computer program code for carrying out operations of the present disclosure may be written in one or more programming languages, including, but not limited to, an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The modules described in the embodiments of the present disclosure may be implemented in software or hardware. The name of the module is not limited to the module itself in some cases, and for example, the acquisition module may also be described as "a module for acquiring an interface document corresponding to the target interface".

The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), an Application Specific Standard Product (ASSP), a system on a chip (SOC), a Complex Programmable Logic Device (CPLD), and the like.

In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

The foregoing description is only of the preferred embodiments of the present disclosure and description of the principles of the technology being employed. It will be appreciated by persons skilled in the art that the scope of the disclosure referred to in this disclosure is not limited to the specific combinations of features described above, but also covers other embodiments which may be formed by any combination of features described above or equivalents thereof without departing from the spirit of the disclosure. Such as those described above, are mutually substituted with the technical features having similar functions disclosed in the present disclosure (but not limited thereto).

Moreover, although operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of the present disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.

Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are example forms of implementing the claims. The specific manner in which the various modules perform the operations in the apparatus of the above embodiments have been described in detail in connection with the embodiments of the method, and will not be described in detail herein.

Claims

1. A document processing method, the method comprising:

2. The method of claim 1, wherein the interface configuration data includes first information corresponding to the target interface, the first information being editable information; the updating the interface document and the interface configuration data according to the information adjustment instruction includes:

3. The method of claim 2, wherein the first information comprises at least one of:

descriptive information of the target interface;

4. The method according to claim 1, wherein the method further comprises:

5. The method according to claim 1, wherein the method further comprises:

6. The method of claim 5, wherein the method further comprises:

receiving an audit instruction;

7. The method of claim 2, wherein the interface configuration data further includes second information corresponding to the target interface, the second information being non-editable information.

8. The method of claim 7, wherein the second information comprises at least one of: interface name, request address, request mode, request instance, reply instance, error code.

9. The method according to any one of claims 1 to 8, wherein the obtaining the interface document corresponding to the target interface includes:

determining the target interface;

10. A document processing apparatus, the apparatus comprising:

11. A computer readable medium on which a computer program is stored, characterized in that the computer program, when being executed by a processing device, implements the steps of the method according to any one of claims 1 to 9.

12. An electronic device, comprising:

a storage device having a computer program stored thereon;

processing means for executing said computer program in said storage means to carry out the steps of the method of any one of claims 1 to 9.