Here is the original discuss issue[1] (two more months ago) I think we can move this tool from `apisix-dashboard` to `apisix` first. Then the dashboard can copy the JSON schema file directly from APISIX project.
[1] https://github.com/apache/apisix/issues/2247 On Tue, Nov 3, 2020 at 10:08 AM Ming Wen <[email protected]> wrote: > hello, dev, > This discussion was on github[1] at the beginning, and because of its > importance, I synced it to the mailing list. > > Because the dashboard project requires schema verification for plug-ins, > upstreams, etc., and the definition of the schema is written in the Lua > code of Apache APISIX. Therefore, we need a tool to generate a json schema > file based on the Lua code of Apache APISIX so that it can be used by the > Go and front-end code of the dashboard project. > > The current approach is: > 1. Integrate this tool in the dashboard project, mock the environment and > dependent libraries of Apache APISIX; > 2. After Apache APISIX modifies the plug-in schema, the code of the > dashboard project needs to be modified synchronously; > In addition, how do we deal with user-defined plug-ins? > > And what I hope to achieve in the end is: > > 1. The tool for synchronizing schema has nothing to do with the > dashboard project. After all, this is a product that the data plane > should > generate; > 2. When the schema of the data plane changes, there is no need to modify > the code of this tool; > 3. The dashboard project should not depend on Lua. > > what do you think? > > [1] https://github.com/apache/apisix-dashboard/issues/605 > > Thanks, > Ming Wen, Apache APISIX & Apache SkyWalking > Twitter: _WenMing > -- *MembPhis* My GitHub: https://github.com/membphis Apache APISIX: https://github.com/apache/apisix
