CN116521732A - YApi label-based interface query method and device, storage medium and electronic device - Google Patents
YApi label-based interface query method and device, storage medium and electronic device Download PDFInfo
- Publication number
- CN116521732A CN116521732A CN202310293672.5A CN202310293672A CN116521732A CN 116521732 A CN116521732 A CN 116521732A CN 202310293672 A CN202310293672 A CN 202310293672A CN 116521732 A CN116521732 A CN 116521732A
- Authority
- CN
- China
- Prior art keywords
- interface
- yapi
- target
- label
- information
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 64
- 238000004590 computer program Methods 0.000 claims description 9
- 238000012545 processing Methods 0.000 claims description 6
- 230000004044 response Effects 0.000 claims description 3
- 238000004458 analytical method Methods 0.000 abstract description 10
- 238000013461 design Methods 0.000 abstract description 10
- 238000004891 communication Methods 0.000 description 5
- 238000010586 diagram Methods 0.000 description 5
- 238000011161 development Methods 0.000 description 4
- 230000018109 developmental process Effects 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 238000004519 manufacturing process Methods 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 230000011218 segmentation Effects 0.000 description 3
- 229920001971 elastomer Polymers 0.000 description 2
- 239000000806 elastomer Substances 0.000 description 2
- 230000008676 import Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000007405 data analysis Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
- G06F16/24553—Query execution of query operations
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computational Linguistics (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
The application discloses an interface query method and device based on YApi labels, a storage medium and an electronic device, and relates to the technical field of computers, wherein the interface query method based on YApi labels comprises the following steps: acquiring business keywords input by a user; inquiring a target label matched with the service keyword from a target database based on the service keyword to obtain interface information of at least one interface associated with the target label; displaying interface information of at least one interface to a user; wherein the target tag is a YApi tag; the target database is an interface information database created based on YApi tags. The YApi label-based interface query method, device, storage medium and electronic device are used for facilitating the query of a developer on the basis of the YApi label, and avoiding missing of interfaces in a demand design analysis stage.
Description
Technical Field
The application relates to the technical field of computers, in particular to an interface query method and device based on YApi labels, a storage medium and an electronic device.
Background
YApi is an efficient, easy-to-use, powerful application program interface (Application Programming Interface, API) management platform capable of providing convenient interface management services for development, production and testers.
In the related art, in the project development process, a developer classifies and maintains the interface document under different projects of YApi according to different use scenes, calling platforms and other modes. Because the YApi interface management platform is managed based on projects, interfaces are easy to miss in a demand design analysis stage, and full-scale effective coverage analysis cannot be carried out on the demand influence interfaces, so that the demand design is missed.
Based on this, a tool capable of retrieving interfaces according to business keywords is urgently needed to make up for the functional shortages of the YApi interface management platform.
Disclosure of Invention
The purpose of the application is to provide an interface query method and device based on YApi labels, a storage medium and an electronic device, which are used for facilitating developers to query interfaces based on the YApi labels and avoiding missing interfaces in a demand design analysis stage.
The application provides an interface query method based on YApi labels, which comprises the following steps:
acquiring business keywords input by a user; inquiring a target label matched with the business keyword from a target database based on the business keyword to obtain interface information of at least one interface associated with the target label; displaying interface information of the at least one interface to a user; wherein the target tag is a YApi tag; the target database is an interface information database created based on the YApi label.
Optionally, after the presenting the interface information of the at least one interface to the user, the method further includes: responsive to a selection input by a user selecting a target interface from the at least one interface, presenting to the user a business document associated with the target interface and/or caller information associated with the target interface.
Optionally, before the querying, based on the service keyword, a target tag matched with the service keyword from a target database, and obtaining interface information of at least one interface associated with the target tag, the method further includes: acquiring interface information of each of a plurality of interfaces and YApi labels of each interface from a YApi interface management platform through an open interface provided by the YApi interface management platform; creating the target database based on interface information of each of the plurality of interfaces and YApi tags of each interface; wherein the plurality of interfaces are interfaces managed by the YApi interface management platform.
Optionally, after the creating the target database based on the interface information of each of the plurality of interfaces and the YApi tag of each interface, the method further comprises: and associating the target business document matched with the target business information with the target interface to be associated based on the target business information indicated by the interface information of any target interface to be associated in the plurality of interfaces.
Optionally, after the creating the target database based on the interface information of each of the plurality of interfaces and the YApi tag of each interface, the method further comprises: and associating the caller information of the target caller matched with the target call information with the target interface to be associated based on the target call information indicated by the interface information of any target interface to be associated in the plurality of interfaces.
The application also provides an interface inquiry device based on the YApi label, which comprises:
the acquisition module is used for acquiring the business keywords input by the user; the query module is used for querying a target label matched with the service keyword from a target database based on the service keyword to obtain interface information of at least one interface associated with the target label; the display module is used for displaying interface information of the at least one interface to a user; wherein the target tag is a YApi tag; the target database is an interface information database created based on the YApi label.
Optionally, the presentation module is further configured to present, to the user, a service document associated with the target interface and/or caller information associated with the target interface in response to a selection input by the user selecting the target interface from the at least one interface.
Optionally, the apparatus further comprises: a data synchronization module and a data processing module; the data synchronization module is used for acquiring interface information of each of a plurality of interfaces and YApi labels of each interface from the YApi interface management platform through an open interface provided by the YApi interface management platform; the data processing module is used for creating the target database based on the interface information of each of the plurality of interfaces and the YApi label of each interface; wherein the plurality of interfaces are interfaces managed by the YApi interface management platform.
Optionally, the apparatus further comprises: a data association module; the data association module is used for associating the target business document matched with the target business information with the target interface to be associated based on the target business information indicated by the interface information of any one of the interfaces to be associated.
Optionally, the data association module is further configured to associate caller information of a target caller matched with the target call information with the target interface to be associated based on the target call information indicated by the interface information of any target interface to be associated in the multiple interfaces.
The present application also provides an electronic device comprising a memory and a processor, the memory having stored therein a computer program, the processor being arranged to perform the steps of implementing the YApi tag based interface query method as described in any of the above by means of the computer program.
The present application also provides a computer readable storage medium comprising a stored program, wherein the program when executed implements the steps of the YApi label based interface query method as described in any one of the above.
The present application also provides a computer program product comprising a computer program which when executed by a processor implements the steps of the YApi tag based interface query method as described in any one of the above.
According to the YApi label-based interface query method, device, storage medium and electronic device, firstly, service keywords input by a user are obtained; then, inquiring a target label matched with the service keyword from a target database based on the service keyword to obtain interface information of at least one interface associated with the target label; finally, displaying interface information of at least one interface to a user; wherein the target tag is a YApi tag; the target database is an interface information database created based on YApi tags. Therefore, developers can query interfaces based on the YApi label, and interfaces are prevented from being omitted in a demand design analysis stage.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.
In order to more clearly illustrate the technical solutions of the present application or the prior art, the following description will briefly introduce the drawings used in the embodiments or the description of the prior art, and it is obvious that, in the following description, the drawings are some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is one of the flow diagrams of the YApi tag-based interface query method provided herein;
FIG. 2 is a second flow chart of the YApi tag-based interface query method provided in the present application;
FIG. 3 is a schematic diagram of the structure of the YApi tag-based interface query device provided herein;
fig. 4 is a schematic structural diagram of an electronic device provided in the present application.
Detailed Description
In order to make the present application solution better understood by those skilled in the art, the following description will be made in detail and with reference to the accompanying drawings in the embodiments of the present application, it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, shall fall within the scope of the present application.
It should be noted that the terms "first," "second," and the like in the description and claims of the present application and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that embodiments of the present application described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
The following is an explanation of the terms of art referred to in the examples of the present application:
YApi is an efficient, easy-to-use, powerful application program interface (Application Programming Interface, API) management platform capable of providing convenient interface management services for development, production and testers. After the developer successfully creates the project, the application program interface can be added under the project by means of manual addition or data import, and the interface is tested. However, since the YApi interface management platform performs interface management based on items, many interfaces commonly used by a plurality of items are not all displayed in the interface list of the items. This results in a missing interface when the developer analyzes the interface in the design of demand analysis phase.
The elastiscearch is a distributed, highly extended, high real-time search and data analysis engine. The method can conveniently enable a large amount of data to have the capabilities of searching, analyzing and exploring. The horizontal scalability of the elastomer search is fully utilized, enabling the data to become more valuable in a production environment. The implementation principle of the elastic search is mainly divided into the following steps, firstly, a user submits data to an elastic search database, then a word segmentation controller is used for word segmentation of corresponding sentences, the weight and word segmentation results are stored in the data together, when the user searches the data, the results are ranked according to the weight, scoring is carried out, and then the returned results are presented to the user.
Aiming at the technical problems of the YApi interface management platform in the related art, the embodiment of the application provides an interface query method based on the YApi label, which can establish the YApi label to realize the purpose of associating interface management with business and realize the interface information query function based on the YApi label.
The method for querying the interface based on the YApi label provided by the embodiment of the application is described in detail through specific embodiments and application scenes thereof with reference to the accompanying drawings.
As shown in fig. 1, an interface query method based on YApi label provided in an embodiment of the present application may include the following steps 101 to 103:
step 101, acquiring business keywords input by a user.
The service keywords are exemplary keywords used by the developer for interface retrieval in the embodiment of the application, and the service keywords may be related to a service type, an interface type or an interface meaning.
For example, the service keyword may be "mobile payment", or "login scenario", etc.
And 102, inquiring a target label matched with the business keyword from a target database based on the business keyword to obtain interface information of at least one interface associated with the target label.
Wherein the target tag is a YApi tag; the target database is an interface information database created based on the YApi label.
Illustratively, in the YApi interface management platform, a developer may set a plurality of YApi tags (i.e., tags) for each interface, and in the embodiment of the present application, the target database may be constructed based on the YApi tags set by the developer for each interface in the YApi interface management platform, and the interface information of each interface.
Illustratively, the target database may be a database of an elastomer search engine, which is mainly used for querying interface information. The interface information may include at least one of: interface name, interface path (call path of interface), interface document, request method (including POST method, GET method, etc.), interface classification, belonging project, etc.
For example, as shown in fig. 2, a user may set a TAG (i.e., YApi TAG) for each interface (including interfaces 1, 2, 3, 4, 5, etc.) in the YApi interface management platform, and then the synchronization service may obtain the YApi TAG of each interface and the interface information of each interface from the YApi interface management platform by calling an open interface (openapi) provided by the YApi interface management platform, and store the obtained data in a database of the elastic search engine.
It should be noted that, in the YApi interface management platform, the YApi TAG of the interface is used only as a TAG, and the YApi interface management platform also does not provide an interface retrieval function based on the YApi TAG.
Step 103, displaying interface information of the at least one interface to a user.
For example, the interface information of the at least one interface may be presented in a front-end page, which is different from the page provided by the YApi interface management platform. Because YApi is developed based on the node. Js framework, the related professionals are fewer, and the learning cost of the node. Js is higher, the data synchronization function for acquiring data from the YApi interface management platform provided by the embodiment of the application can be developed by using Java language, so that the development cost is reduced.
It should be noted that, the interface query method based on the YApi label provided in the embodiment of the present application has the following technical effects: after the user inputs a service keyword in a search box of a TAG (TAG) search page, the elastic search engine returns interface information of at least one interface containing a target TAG, wherein the target TAG is a YApi TAG matched with the service keyword.
By way of example, taking the above-mentioned business keyword as "mobile payment", after searching through the elastic search engine based on the business keyword, all interfaces containing YApi labels related to "mobile payment" can be returned, so as to implement interface query based on YApi labels.
Optionally, in the embodiment of the present application, after displaying the queried interface information of at least one interface to the user, detailed information of a certain interface may be further displayed to the user according to a selection of the user.
Illustratively, after the step 103, the YApi tag-based interface query method provided in the embodiments of the present application may further include the following step 104:
step 104, responsive to a selection input by a user selecting a target interface from the at least one interface, presenting to the user a business document associated with the target interface and/or caller information associated with the target interface.
The selection input may be, for example, a selection input for selecting any target interface from a presentation page presenting the at least one interface. In the display page of the at least one interface, interface information of the at least one interface may be displayed in a list form.
By way of example, the service document and the caller information can facilitate a developer to further understand the interface, so that in the stage of the demand design analysis of the interface, whether the interface needs to perform the demand design analysis is judged according to the service document and the caller information, and omission is avoided.
It should be noted that not all interfaces have business documents, nor do all interfaces have caller information, and based on this, presentation can be performed to a user according to information contained in the interfaces.
Optionally, in the embodiment of the present application, in order to implement the YApi tag-based interface query, the creation of the relevant database is also required.
Illustratively, before the step 102, the YApi tag-based interface query method provided in the embodiments of the present application may further include the following steps 105 and 106:
step 105, obtaining interface information of each of a plurality of interfaces and YApi labels of each interface from the YApi interface management platform through an open interface provided by the YApi interface management platform.
Step 106, creating the target database based on the interface information of each of the plurality of interfaces and the YApi label of each interface.
Wherein the plurality of interfaces are interfaces managed by the YApi interface management platform.
Illustratively, since the YApi interface management platform does not provide the YApi tag-based interface retrieval service, in order to implement the YApi tag-based interface query, it is necessary to import data into an elastic search engine in which the YApi tag-based interface query is implemented.
Optionally, in the embodiment of the present application, since association between the interface and the service document and association between the interface and the caller information cannot be implemented in the YApi interface management platform, it is necessary to associate the interface with the service document and caller information after creating the above-mentioned target database.
Illustratively, after the step 106 and before the step 102, the YApi tag-based interface query method provided in the embodiments of the present application may further include the following step 107 and/or step 108:
and step 107, associating the target business document matched with the target business information with the target interface to be associated based on the target business information indicated by the interface information of any one of the interfaces to be associated.
And step 108, associating the caller information of the target caller matched with the target caller information with the target interface to be associated based on the target caller information indicated by the interface information of any target interface to be associated in the plurality of interfaces.
In the embodiment of the application, the automatic association of the caller information and the service document can be performed through the target call information indicated by the interface information and the target service information indicated by the interface information, and the manual association function can be provided when the automatic association of the information cannot be realized.
According to the YApi label-based interface query method, firstly, business keywords input by a user are obtained; then, inquiring a target label matched with the service keyword from a target database based on the service keyword to obtain interface information of at least one interface associated with the target label; finally, displaying interface information of at least one interface to a user; wherein the target tag is a YApi tag; the target database is an interface information database created based on YApi tags. Therefore, developers can query interfaces based on the YApi label, and interfaces are prevented from being omitted in a demand design analysis stage.
It should be noted that, in the YApi tag-based interface query method provided in the embodiments of the present application, the execution subject may be a YApi tag-based interface query device, or a control module in the YApi tag-based interface query device for executing the YApi tag-based interface query method. In the embodiment of the application, the YApi label-based interface query device executes the YApi label-based interface query method as an example, and the YApi label-based interface query device provided in the embodiment of the application is described.
In the embodiment of the application, the method is shown in the drawings. The YApi label-based interface query method is exemplified by a drawing in combination with the embodiment of the application. In specific implementation, the YApi label-based interface query method shown in the above method drawings may be further implemented in combination with any other drawing that may be combined and is illustrated in the above embodiment, which is not described herein.
The YApi-tag-based interface query device provided in the present application is described below, and the hereinafter described YApi-tag-based interface query method and the above described YApi-tag-based interface query method may be referred to correspondingly to each other.
Fig. 3 is a schematic structural diagram of an interface query device based on YApi tag according to an embodiment of the present application, and as shown in fig. 3, specifically includes:
an obtaining module 301, configured to obtain a service keyword input by a user; a query module 302, configured to query, from a target database, a target tag that matches the service keyword based on the service keyword, to obtain interface information of at least one interface associated with the target tag; a display module 303, configured to display interface information of the at least one interface to a user; wherein the target tag is a YApi tag; the target database is an interface information database created based on the YApi label.
Optionally, the presenting module 303 is further configured to present, to the user, a service document associated with the target interface and/or caller information associated with the target interface, in response to a selection input by the user selecting the target interface from the at least one interface.
Optionally, the apparatus further comprises: a data synchronization module and a data processing module; the data synchronization module is used for acquiring interface information of each of a plurality of interfaces and YApi labels of each interface from the YApi interface management platform through an open interface provided by the YApi interface management platform; the data processing module is used for creating the target database based on the interface information of each of the plurality of interfaces and the YApi label of each interface; wherein the plurality of interfaces are interfaces managed by the YApi interface management platform.
Optionally, the apparatus further comprises: a data association module; the data association module is used for associating the target business document matched with the target business information with the target interface to be associated based on the target business information indicated by the interface information of any one of the interfaces to be associated.
Optionally, the data association module is further configured to associate caller information of a target caller matched with the target call information with the target interface to be associated based on the target call information indicated by the interface information of any target interface to be associated in the multiple interfaces.
The interface query device based on the YApi label firstly obtains business keywords input by a user; then, inquiring a target label matched with the service keyword from a target database based on the service keyword to obtain interface information of at least one interface associated with the target label; finally, displaying interface information of at least one interface to a user; wherein the target tag is a YApi tag; the target database is an interface information database created based on YApi tags. Therefore, developers can query interfaces based on the YApi label, and interfaces are prevented from being omitted in a demand design analysis stage.
Fig. 4 illustrates a physical schematic diagram of an electronic device, as shown in fig. 4, which may include: processor 410, communication interface (Communications Interface) 420, memory 430 and communication bus 440, wherein processor 410, communication interface 420 and memory 430 communicate with each other via communication bus 440. The processor 410 may invoke logic instructions in the memory 430 to perform a YApi tag based interface query method comprising: acquiring business keywords input by a user; inquiring a target label matched with the business keyword from a target database based on the business keyword to obtain interface information of at least one interface associated with the target label; displaying interface information of the at least one interface to a user; wherein the target tag is a YApi tag; the target database is an interface information database created based on the YApi label.
Further, the logic instructions in the memory 430 described above may be implemented in the form of software functional units and may be stored in a computer-readable storage medium when sold or used as a stand-alone product. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
In another aspect, the present application also provides a computer program product comprising a computer program stored on a computer readable storage medium, the computer program comprising program instructions which, when executed by a computer, enable the computer to perform the YApi-tag based interface query method provided by the methods described above, the method comprising: acquiring business keywords input by a user; inquiring a target label matched with the business keyword from a target database based on the business keyword to obtain interface information of at least one interface associated with the target label; displaying interface information of the at least one interface to a user; wherein the target tag is a YApi tag; the target database is an interface information database created based on the YApi label.
In still another aspect, the present application further provides a computer readable storage medium, where the computer readable storage medium includes a stored program, where the program executes the YApi tag-based interface query method provided by the methods above, and the method includes: acquiring business keywords input by a user; inquiring a target label matched with the business keyword from a target database based on the business keyword to obtain interface information of at least one interface associated with the target label; displaying interface information of the at least one interface to a user; wherein the target tag is a YApi tag; the target database is an interface information database created based on the YApi label.
The apparatus embodiments described above are merely illustrative, wherein the elements illustrated as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art will understand and implement the present invention without undue burden.
From the above description of the embodiments, it will be apparent to those skilled in the art that the embodiments may be implemented by means of software plus necessary general hardware platforms, or of course may be implemented by means of hardware. Based on this understanding, the foregoing technical solution may be embodied essentially or in a part contributing to the prior art in the form of a software product, which may be stored in a computer readable storage medium, such as ROM/RAM, a magnetic disk, an optical disk, etc., including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method described in the respective embodiments or some parts of the embodiments.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present application, and are not limiting thereof; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the corresponding technical solutions.
Claims (10)
1. An interface query method based on YApi labels is characterized by comprising the following steps:
acquiring business keywords input by a user;
inquiring a target label matched with the business keyword from a target database based on the business keyword to obtain interface information of at least one interface associated with the target label;
displaying interface information of the at least one interface to a user;
wherein the target tag is a YApi tag; the target database is an interface information database created based on the YApi label.
2. The YApi label based interface query method of claim 1, wherein after the presenting the interface information of the at least one interface to the user, the method further comprises:
responsive to a selection input by a user selecting a target interface from the at least one interface, presenting to the user a business document associated with the target interface and/or caller information associated with the target interface.
3. The YApi label-based interface query method of claim 1, wherein the query of a target label matching the business key from a target database based on the business key, before obtaining interface information of at least one interface associated with the target label, the method further comprises:
acquiring interface information of each of a plurality of interfaces and YApi labels of each interface from a YApi interface management platform through an open interface provided by the YApi interface management platform;
creating the target database based on interface information of each of the plurality of interfaces and YApi tags of each interface;
wherein the plurality of interfaces are interfaces managed by the YApi interface management platform.
4. The YApi label based interface query method of claim 3, wherein the method further comprises, after creating the target database based on the interface information for each of the plurality of interfaces and the YApi label for each interface:
and associating the target business document matched with the target business information with the target interface to be associated based on the target business information indicated by the interface information of any target interface to be associated in the plurality of interfaces.
5. The YApi label based interface query method of claim 4, wherein the method further comprises, after creating the target database based on the interface information for each of the plurality of interfaces and the YApi label for each interface:
and associating the caller information of the target caller matched with the target call information with the target interface to be associated based on the target call information indicated by the interface information of any target interface to be associated in the plurality of interfaces.
6. An YApi tag-based interface query device, the device comprising:
the acquisition module is used for acquiring the business keywords input by the user;
the query module is used for querying a target label matched with the service keyword from a target database based on the service keyword to obtain interface information of at least one interface associated with the target label;
the display module is used for displaying interface information of the at least one interface to a user;
wherein the target tag is a YApi tag; the target database is an interface information database created based on the YApi label.
7. The YApi label based interface query device of claim 6, wherein the device comprises a plurality of interface units,
the presentation module is further configured to present to a user a business document associated with the target interface and/or caller information associated with the target interface in response to a selection input by the user selecting the target interface from the at least one interface.
8. The YApi label based interface query device of claim 6, further comprising: a data synchronization module and a data processing module;
the data synchronization module is used for acquiring interface information of each of a plurality of interfaces and YApi labels of each interface from the YApi interface management platform through an open interface provided by the YApi interface management platform;
the data processing module is used for creating the target database based on the interface information of each of the plurality of interfaces and the YApi label of each interface;
wherein the plurality of interfaces are interfaces managed by the YApi interface management platform.
9. A computer-readable storage medium, characterized in that the computer-readable storage medium comprises a stored program, wherein the program when run performs the YApi label based interface query method of any one of claims 1 to 5.
10. An electronic device comprising a memory and a processor, wherein the memory has stored therein a computer program, the processor being arranged to execute the YApi tag based interface query method of any one of claims 1 to 5 by means of the computer program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310293672.5A CN116521732A (en) | 2023-03-23 | 2023-03-23 | YApi label-based interface query method and device, storage medium and electronic device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310293672.5A CN116521732A (en) | 2023-03-23 | 2023-03-23 | YApi label-based interface query method and device, storage medium and electronic device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116521732A true CN116521732A (en) | 2023-08-01 |
Family
ID=87391098
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310293672.5A Pending CN116521732A (en) | 2023-03-23 | 2023-03-23 | YApi label-based interface query method and device, storage medium and electronic device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116521732A (en) |
-
2023
- 2023-03-23 CN CN202310293672.5A patent/CN116521732A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9298721B2 (en) | Prioritized search results based on monitored data | |
| US20080263029A1 (en) | Adaptive archive data management | |
| US20090157729A1 (en) | Methods for generating search engine index enhanced with task-related metadata | |
| US20110047164A1 (en) | Universal Data Relationship Inference Engine | |
| CN103136228A (en) | Image search method and image search device | |
| WO2012061275A1 (en) | Multi-modal approach to search query input | |
| CN107085583B (en) | Electronic document management method and device based on content | |
| US20080147631A1 (en) | Method and system for collecting and retrieving information from web sites | |
| US20190065455A1 (en) | Intelligent form creation | |
| CN111737443B (en) | Answer text processing method and device and key text determining method | |
| CN110489032B (en) | Dictionary query method for electronic book and electronic equipment | |
| CA3051919C (en) | Machine learning (ml) based expansion of a data set | |
| JP2007128450A (en) | Software reusable component management system | |
| CN111160699A (en) | Expert recommendation method and system | |
| US9466003B2 (en) | System and method for using an image to provide search results | |
| CN106844406B (en) | Search method and search device | |
| CN109783612B (en) | Report data positioning method and device, storage medium and terminal | |
| US7263519B2 (en) | Process for searching a repository of resources | |
| CN108255888B (en) | Data processing method and system | |
| CN116521732A (en) | YApi label-based interface query method and device, storage medium and electronic device | |
| CN115858742A (en) | Question text expansion method, device, equipment and storage medium | |
| CN115422270A (en) | Information processing method and device | |
| CN110502690B (en) | Classified search method and device | |
| CN115796465A (en) | OKR information display method, device, equipment and storage medium | |
| CN109408713B (en) | Software demand retrieval system based on user feedback information |
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 |