From 1f2f5f336e402fd7150a720914b10a92fa5e41ab Mon Sep 17 00:00:00 2001 From: Jueun Park <s5616012@mailbox.tu-dresden.de> Date: Thu, 31 Mar 2022 13:42:23 +0900 Subject: [PATCH] Edited index.md --- pages/docs/index.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/pages/docs/index.md b/pages/docs/index.md index d81ed720..ada8cf50 100644 --- a/pages/docs/index.md +++ b/pages/docs/index.md @@ -27,13 +27,16 @@ OpenAPIObject ::= <OpenAPI> <JsonSchemaDialect> I:InfoObject Serv:ServerObject There are some implementation details developers must consider: + - JastAdd doesn't support `Map`. So, it must be constructed in a tuple (AST-Node). e.g. `ServerVariablesTuple ::= <Name> S:ServerVariableObject;` <-> `variables` in [Server Object](https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.0.3.md#serverObject) + - In OAS, several objects can be replaced by [Reference Object](https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.0.3.md#referenceObject). In `RAGO`, we implemented this structure in an abstract node to every concerned object. e.g. [Parameter Object](https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.0.3.md#parameterObject) ``` abstract ParameterOb; ParameterReference : ParameterOb ::= <Ref> ...; ParameterObject : ParameterOb ::= <Name> <In> ...; ``` + - Most objects can be extended with `Extension` containing unfixed name and values. In JastAdd, this is also implemented in a tuple (AST-Node) `Extension ::= <Key> <Value:Object>;` ## Fuzzing Methods -- GitLab