Method and device for generating GraphQL front-end operation interface

Abstract

The invention discloses a method and a device for generating a GraphQL front-end operation interface. The method disclosed by the invention comprises the following steps: displaying information of alltypes and objects supported by a GraphQL server to a developer through a GUI; obtaining selection information of a selected object needing to be operated by a developer through the GUI; based on selection information of the selected object, automatically generating a front end operation interface of GraphQL, wherein the type comprises a schema type, the selection information comprises attributesof a selected field in the selected object and specific field values of one or more selected fields, and the front-end operation comprises at least one of query, mutation and subscription. According to the technical scheme, the front-end operation interface can be rapidly generated, and a developer does not need to manually compile codes.

Description

technical field [0001] The invention relates to the field of computer network application development, in particular to a method and device for generating a GraphQL front-end operation interface. Background technique [0002] GraphQL is a revolutionary API tool in the field of computer network application development. Unlike the traditional RESTful API, it does not need to predefine the operation data required by the client on the server side, but allows the client to specify directly in the request. required operational data. [0003] GraphQL is both a query language for APIs and a runtime to satisfy data queries. GraphQL provides a complete set of easy-to-understand descriptions of the data in the API, enabling clients to obtain exactly the data they need without any redundancy, making it easier for the API to evolve over time, and can also be used for Build powerful developer tools. For example, sending a GraphQL request to the GraphQL server through an API implemented...

AI Technical Summary

Problems solved by technology

More specifically, developers currently usually use the (online) help documents provided by GraphQL to quickly query the desired data (including the objects and object types involved, the fields in the objects, the types of fields, etc.), but when the types and fields When there are too many, the cost of manual maintenance is too high, and the data conversion cannot be unified

Therefore, the more complex the page logic, the more types and fields, the greater the writing cost

[0006] In addition, developers will maintain and manage the corresponding interface list in the project according to the type. When the fields of GraphQL change, they also need to modify the schema in the specified file, and the cost of maintenance and management is relatively high.

Moreover, developers do not have a common solution for data maintenance and data conversion. Sometimes it is in the API file, and sometimes it is in the code of the View layer.

Images