CN110333847B - Integration method for automatic document generation of back-end interface - Google Patents

Integration method for automatic document generation of back-end interface Download PDF

Info

Publication number
CN110333847B
CN110333847B CN201910376268.8A CN201910376268A CN110333847B CN 110333847 B CN110333847 B CN 110333847B CN 201910376268 A CN201910376268 A CN 201910376268A CN 110333847 B CN110333847 B CN 110333847B
Authority
CN
China
Prior art keywords
interface
annotation
code
page
comments
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201910376268.8A
Other languages
Chinese (zh)
Other versions
CN110333847A (en
Inventor
蔡灿
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Chongqing Tianpeng Network Co ltd
Original Assignee
Chongqing Tianpeng Network Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Chongqing Tianpeng Network Co ltd filed Critical Chongqing Tianpeng Network Co ltd
Priority to CN201910376268.8A priority Critical patent/CN110333847B/en
Publication of CN110333847A publication Critical patent/CN110333847A/en
Application granted granted Critical
Publication of CN110333847B publication Critical patent/CN110333847B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/30Creation or generation of source code
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/54Interprogram communication
    • G06F9/547Remote procedure calls [RPC]; Web services

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Document Processing Apparatus (AREA)

Abstract

The invention provides an integration method for automatic document generation of a back-end interface. The invention standardizes code annotation in an annotation mode, fills important information defined by an interface in the interface annotation and the interface annotation, automatically forms an interface structure according to products and projects by each department, automatically forms records in a document system, automatically analyzes the code annotation and the annotation when the interface is released, generates a self-defined interface page, and automatically uploads the generated interface display page to the document system after the interface is released, so that the interface display page can be seen by all personnel. The invention mainly solves the problem of the transmission efficiency of the remote calling interface definition among a large number of different technical workers, and solves the problem that different display military interfaces are adopted for different applications.

Description

Integration method for automatic document generation of back-end interface
Technical Field
The invention relates to the technical field of computers, in particular to an integration method for automatic document generation of a back-end interface.
Background
With the development of mobile internet technology, the whole system adopts a micro-service architecture at present, and the back-end application as well as the back-end application and the front-end application adopt remote calling to perform data interaction. The applications are usually developed and maintained by different persons, and the applications are normatively restricted by the interface definition called remotely. As development teams become more and more voluminous, the propagation of interface definitions among personnel becomes a costly task of communication.
Therefore, in long-term research and development, the inventor has conducted intensive research on how to solve the problem of the transfer efficiency of the remote invocation interface definition among a large number of different technical workers, and the problem of different applications adopting different presentation interfaces, and has proposed an integration method for automatic document generation of a backend interface, so as to solve one of the above technical problems.
Disclosure of Invention
The present invention is directed to an integrated method for automatic document generation by a backend interface, which solves at least one of the above-mentioned problems. The specific scheme is as follows:
according to a first aspect, an integrated method for backend interface automatic document generation, according to a specific embodiment of the present invention, the method comprises the steps of,
s1, standardizing code annotation in an annotation mode, and filling important information defined by the interface in the interface annotation and the interface annotation;
s2, each department automatically forms an interface tree structure according to products and projects, and records are automatically formed in a document system;
s3, the interface method distributes automatic analysis code notes and annotations, and generates a self-defined interface page;
and S4, after the interface is released, automatically uploading the generated interface display page to a document system, and enabling the whole person to see the interface display page.
According to the second aspect, in the integrated method for automatic document generation of the backend interface, in step S1, the code annotation and annotation are specified in an annotation mode, and each interface definer writes the annotation and annotation according to the specification.
According to a third aspect, an integrated method for automatic document generation by a backend interface includes interface annotation, method annotation, and field annotation.
According to a fourth aspect, an integrated method for automatic document generation by a backend interface is provided, wherein the method comments are used for explaining specific use instructions of the method, and the field comments are used for explaining the meaning of the field.
According to a fifth aspect, an integrated method for automatic document generation for a backend interface, the interface annotation and method annotation necessarily include author, page title.
According to the specific implementation manner of the present invention, in a sixth aspect, an integration method for automatic document generation of a backend interface is provided, in the step S2, each department automatically forms an interface tree structure according to products and items, when writing an interface code, the interface code needs to be written according to specifications, before the interface code is issued, field detection code annotations and notes are provided, and interface codes which do not meet the specifications are not issued.
According to the specific implementation manner of the present invention, in the seventh aspect, when writing the interface code, each department needs to write according to the specification, and reminds the developer of the code position which is not in accordance with the specification by a technical means, so as to ensure that the code annotation and annotation can correctly generate the document.
According to the specific implementation manner of the invention, in an eighth aspect, an integration method for automatic document generation of a backend interface is provided, after the interface is published, a generated interface display page is automatically uploaded to a document system, wherein the document system is constructed by using maven.
According to the specific implementation mode of the invention, in a ninth aspect, the invention provides an integration method for automatic document generation of a back-end interface.
According to the specific implementation mode of the invention, in a tenth aspect, an integration method for automatic document generation of a backend interface is provided, wherein an xml format file of java doc automatically generated during packaging is read and analyzed through a self-service program, information of each field is acquired according to a specified format, a page tree structure is generated, a page structure relationship and whether a page exists or not are checked, the existing page is updated, and the non-existing page is created.
According to an eleventh aspect, the present invention provides a computer readable storage medium, on which a computer program is stored, which when executed by a processor, implements the method of editing content in a document as described in any of the above.
According to a twelfth aspect of the present invention, there is provided an electronic apparatus, comprising: one or more processors; storage means for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to implement a method of editing content in a document as claimed in any preceding claim.
Compared with the prior art, the scheme of the embodiment of the invention at least has the following beneficial effects:
the invention mainly solves the problem of the transmission efficiency of the remote calling interface definition among a large number of different technical workers, and solves the problem that different applications adopt different display interfaces. On the premise of the technical scheme, the invention can improve the efficiency of information transmission among different technical workers, can display the same annotation and annotation in different applications or different display interfaces of the different applications, and generates a document through the annotation and annotation.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention. It is obvious that the drawings in the following description are only some embodiments of the invention, and that for a person skilled in the art, other drawings can be derived from them without inventive effort. In the drawings:
FIG. 1 shows a flow diagram of a method according to an embodiment of the invention;
FIG. 2 shows a state diagram according to an embodiment of the invention;
fig. 3 shows a schematic diagram of an electronic device connection structure according to an embodiment of the invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention clearer, the present invention will be described in further detail with reference to the accompanying drawings, and it is apparent that the described embodiments are only a part of the embodiments of the present invention, not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The terminology used in the embodiments of the invention is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the examples of the present invention and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise, and "a plurality" typically includes at least two.
It should be understood that the term "and/or" as used herein is merely one type of association that describes an associated object, meaning that three relationships may exist, e.g., a and/or B may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.
It should be understood that although the terms first, second, third, etc. may be used to describe … … in embodiments of the present invention, these … … should not be limited to these terms. These terms are used only to distinguish … …. For example, the first … … can also be referred to as the second … … and similarly the second … … can also be referred to as the first … … without departing from the scope of embodiments of the present invention.
The words "if", as used herein, may be interpreted as "at … …" or "at … …" or "in response to a determination" or "in response to a detection", depending on the context. Similarly, the phrases "if determined" or "if detected (a stated condition or event)" may be interpreted as "when determined" or "in response to a determination" or "when detected (a stated condition or event)" or "in response to a detection (a stated condition or event)", depending on the context.
It is also noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that an article or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such article or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in the article or device in which the element is included.
Alternative embodiments of the present invention are described in detail below with reference to the accompanying drawings.
Example 1
An integrated method for backend interface automatic document generation, wherein the method comprises the steps of:
s1, the code annotation is normalized in annotation mode, and the important information of the interface definition is filled in the interface annotation and the interface annotation
And S2, automatically forming an interface tree structure according to the products and the projects by each department, and automatically forming records in the document system.
And S3, automatically analyzing the code annotation and annotation when the interface is released, and generating a self-defined interface page.
And S4, after the interface is published, automatically uploading the generated interface display page to a document system, and enabling the whole person to see the interface display page.
Example 2
An integrated method for backend interface automatic document generation, wherein the method comprises the steps of:
first, define interface code note specification, annotation specification, each interface definer writes note and annotation according to the specification. Interface comments, method comments and field comments are specified, the interface comments explain the main function set of the interface of the book, the method comments explain the specific use instructions of the method, and the field comments explain the meaning of the field of the book. The interface comments and method comments must contain the author, the page title. A field may be annotated with @ NotNull or @ NotEmpty, indicating that it may not be empty, and this information will be shown in the document.
Next, when writing interface codes, each department needs to write according to the specification; by the technical means, before the interface code is published, the field detects the code annotation and annotation, the interface code which does not meet the specification is not published, and meanwhile, a developer is reminded of the code position which does not meet the specification, so that the code annotation and annotation can be ensured to correctly generate the document.
Finally, analyzing the interface code annotation and annotation, generating a document page and uploading the document page to a document system; the project is constructed by maven, an xml format file of javadoc is automatically generated when the interface code is packaged, the xml file is read and analyzed by a self-service program, and each field information is obtained according to a specified format; generating a page tree structure; checking the page structure relationship and whether the page exists, updating the existing page, and creating the nonexistent page.
Example 3
An integration method for automatic document generation of a back-end interface is disclosed, wherein a project constructed by maven is adopted, and the project is configured as follows:
Figure GDA0002133355790000061
Figure GDA0002133355790000062
example 4
As shown in fig. 3, the present embodiment provides an electronic device for an integrated method of automatic document generation by a backend interface, the electronic device including: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the one processor to be executed by the at least one processor to enable the at least one processor to implement the above-described methods by invoking one or more instructions or sets of instructions, executable programs, etc. stored in the above-described memory.
Example 5
The embodiment of the disclosure provides a nonvolatile computer storage medium, wherein the computer storage medium stores computer executable instructions, and the computer executable instructions can execute the integration method of automatic document generation of a backend interface in any method embodiment.
As shown in fig. 3, a schematic diagram of an electronic device 400 suitable for implementing embodiments of the present disclosure is shown. The terminal device in the embodiments of the present disclosure may include, but is not limited to, a mobile terminal such as a mobile phone, a notebook computer, a digital broadcast receiver, a PDA (personal digital assistant), a PAD (tablet computer), a PMP (portable multimedia player), a vehicle terminal (e.g., a car navigation terminal), and the like, and a stationary terminal such as a digital TV, a desktop computer, and the like. The electronic device is only an example and should not bring any limitations to the functionality and scope of use of the embodiments of the present disclosure.
As shown in fig. 3, electronic device 400 may include a processing device (e.g., central processing unit, graphics processor, etc.) 401 that may perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)402 or a program loaded from a storage device 408 into a Random Access Memory (RAM) 403. In the RAM 403, various programs and data necessary for the operation of the electronic apparatus 400 are also stored. The processing device 401, the ROM 402, and the RAM 403 are connected to each other via a bus 404. An input/output (I/O) interface 405 is also connected to bus 404.
In general, input devices 406 including, for example, a touch screen, touch pad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc., output devices 407 including, for example, a liquid crystal display (L CD), speaker, vibrator, etc., storage devices 408 including, for example, magnetic tape, hard disk, etc., and communication devices 409 may allow electronic device 400 to communicate wirelessly or wiredly with other devices to exchange data although FIG. 3 illustrates electronic device 400 with various means, it is to be understood that not all of the illustrated means are required to be implemented or provided.
In particular, according to an embodiment of the present disclosure, the processes described above with reference to the 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 computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication device 409, or from the storage device 408, or from the ROM 402. The computer program performs the above-described functions defined in the methods of the embodiments of the present disclosure when executed by the processing device 401.
It should be noted that the computer readable medium in the present disclosure can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination 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 present 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 contrast, in the present disclosure, a computer readable signal medium may comprise a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. 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, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.
The computer readable medium may be embodied in the electronic device; or may exist separately without being assembled 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 at least two internet protocol addresses; sending a node evaluation request comprising the at least two internet protocol addresses to node evaluation equipment, wherein the node evaluation equipment selects the internet protocol addresses from the at least two internet protocol addresses and returns the internet protocol addresses; receiving an internet protocol address returned by the node evaluation equipment; wherein the obtained internet protocol address indicates an edge node in the content distribution network.
Alternatively, the computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: receiving a node evaluation request comprising at least two internet protocol addresses; selecting an internet protocol address from the at least two internet protocol addresses; returning the selected internet protocol address; wherein the received internet protocol address indicates an edge node in the content distribution network.
Computer program code for carrying out operations of the present disclosure may be written in any combination of one or more programming languages, including 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 flowchart 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 units described in the embodiments of the present disclosure may be implemented by software or hardware. Where the name of an element does not in some cases constitute a limitation on the element itself.
That is, the integration method for automatic document generation by a backend interface according to the present application can write and package codes in an existing computer-recognizable programming language, and then can implement the above-mentioned flowcharts shown in fig. 1 to 2 in the form of executable programs or instructions or instruction sets. Further, the executable program or instruction set written and packaged in the code of the above-mentioned programming language recognizable by the computer is stored on the non-volatile storage medium, and the storage medium can be recognized and executed by the electronic device or the system constituted by the electronic device described in any of the above paragraphs, and the steps, methods and principles of the recognition and execution belong to the methods or flows shown in fig. 1 to fig. 2.

Claims (5)

1. An integrated method for automatic document generation by a backend interface, the method comprising the steps of,
s1, standardizing code annotation in an annotation mode, and filling important information defined by the interface in the interface annotation and the interface annotation;
s2, each department automatically forms an interface tree structure according to products and projects, and records are automatically formed in a document system;
s3, automatically analyzing the code annotation and annotation when the interface is released, and generating a self-defined interface page;
s4, after the interface is released, automatically uploading the generated interface display page to a document system, and enabling the whole person to see the interface display page;
in the step S2, each department automatically forms an interface tree structure according to the product and the project, when writing the interface code, the interface code needs to be written according to the specification, and before issuing the interface code, the field detection code annotation and annotation is performed by the technical means, and the interface code which does not meet the specification is not issued;
when writing the interface code, each department needs to write according to the specification, and reminds a developer of the code position which is not in accordance with the specification through a technical means, so that the code annotation and annotation can be ensured to correctly generate a document;
after the interface is released, automatically uploading the generated interface display page to a document system, wherein the document system is constructed by maven;
when the interface is issued, the interface code needs to be packaged, and when the interface code is packaged, an xm l format file of javadoc is automatically generated;
analyzing, acquiring information of each field according to a specified format, generating a page tree structure, checking the page structure relationship and whether a page already exists, updating the existing page, and creating a non-existing page.
2. The integrated method for automatic document generation by backend interface according to claim 1, wherein the code annotation, annotation is specified in a annotation manner in step S1, and each interface definer writes the annotation and annotation according to the specification.
3. The integrated method of backend interface automatic document generation according to claim 2, wherein the comments and annotations include interface comments, method comments, field comments.
4. The integrated method for backend interface automatic document generation according to claim 3, wherein the method comments are used to explain the specific use description of the method, and the field comments are used to explain the meaning of the present field.
5. The integrated method of backend interface automatic document generation according to claim 4, characterized by, that the interface comments and method comments must include author, page title.
CN201910376268.8A 2019-05-07 2019-05-07 Integration method for automatic document generation of back-end interface Active CN110333847B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201910376268.8A CN110333847B (en) 2019-05-07 2019-05-07 Integration method for automatic document generation of back-end interface

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910376268.8A CN110333847B (en) 2019-05-07 2019-05-07 Integration method for automatic document generation of back-end interface

Publications (2)

Publication Number Publication Date
CN110333847A CN110333847A (en) 2019-10-15
CN110333847B true CN110333847B (en) 2020-08-04

Family

ID=68139597

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910376268.8A Active CN110333847B (en) 2019-05-07 2019-05-07 Integration method for automatic document generation of back-end interface

Country Status (1)

Country Link
CN (1) CN110333847B (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103049271A (en) * 2012-12-27 2013-04-17 微梦创科网络科技(中国)有限公司 Method and device for automatically generating description document of API (application program interface)
CN107463376A (en) * 2017-07-21 2017-12-12 珠海牛角科技有限公司 The method and device for automatically generating back end interface document based on Javadoc
CN108762808A (en) * 2018-05-17 2018-11-06 李伟荣 The generation method and system of interface document
CN108959076A (en) * 2018-06-25 2018-12-07 浙江网新恒天软件有限公司 A kind of API on-line debugging method

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080002830A1 (en) * 2006-04-14 2008-01-03 Cherkasov Aleksey G Method, system, and computer-readable medium to maintain and/or purge files of a document management system
US8346534B2 (en) * 2008-11-06 2013-01-01 University of North Texas System Method, system and apparatus for automatic keyword extraction
CN109032663A (en) * 2018-07-09 2018-12-18 深圳市小牛在线互联网信息咨询有限公司 Generation method, device, computer equipment and the storage medium of interface document
CN109491708A (en) * 2018-11-21 2019-03-19 北京锐安科技有限公司 Document structure tree method, system, equipment and medium

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103049271A (en) * 2012-12-27 2013-04-17 微梦创科网络科技(中国)有限公司 Method and device for automatically generating description document of API (application program interface)
CN107463376A (en) * 2017-07-21 2017-12-12 珠海牛角科技有限公司 The method and device for automatically generating back end interface document based on Javadoc
CN108762808A (en) * 2018-05-17 2018-11-06 李伟荣 The generation method and system of interface document
CN108959076A (en) * 2018-06-25 2018-12-07 浙江网新恒天软件有限公司 A kind of API on-line debugging method

Also Published As

Publication number Publication date
CN110333847A (en) 2019-10-15

Similar Documents

Publication Publication Date Title
CN109634598B (en) Page display method, device, equipment and storage medium
CN110489345B (en) Crash aggregation method, device, medium and equipment
CN110489101B (en) Interface simulation method, system, medium and electronic equipment
KR20160051780A (en) Creating inforgraphics from text data in electronic documents
CN112395188B (en) Test-oriented software project development method and device, electronic equipment and storage medium
CN111813465B (en) Information acquisition method, device, medium and equipment
CN105027116A (en) Flat book to rich book conversion in e-readers
US20170003829A1 (en) Graphical user interface facilitating sharing and collaborative editing of electronic documents
US9372616B2 (en) Smart interactive bookmarks
US10672295B2 (en) Accessible metadata in data structures
CN111324258B (en) Method, device, equipment and medium for generating contents of configuration items of multilevel pull-down menu
CN110333847B (en) Integration method for automatic document generation of back-end interface
CN110673908A (en) Interface generation method, device, medium and electronic equipment
CN113094286B (en) Page test method and device, storage medium and electronic equipment
CN111241368B (en) Data processing method, device, medium and equipment
US10782947B2 (en) Systems and methods of diagram transformation
CN113282285A (en) Code compiling method and device, electronic equipment and storage medium
CN109815469A (en) A kind of word editing method, device, medium and electronic equipment
CN111209739A (en) Electronic form, electronic device, storage medium, and electronic form verification method
CN111414106A (en) Title display method and device, electronic equipment and computer readable medium
CN111813663B (en) Pointer type identification method, device, medium and equipment
CN112988276B (en) Resource package generation method and device, electronic equipment and storage medium
CN111753080B (en) Method and device for outputting information
CN114997120B (en) Method, device, terminal and storage medium for generating document tag
CN113448550B (en) Method and device for realizing collection management of classes, electronic equipment and computer medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant