René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"QAPage","mainEntity":{"@type":"Question","name":"Should SerializeV2WithoutReference resolve in object references as well?","text":"
Hi,
\n
SerializeV2WithoutReference currently only resolves top-level reference & uses internally SerializeV2 for properties of the AsyncApiSchema.
\n
In my use-case I am trying to extract payload schema to validate my de-serialized model in test against schema with JsonSchema package.
\nIn my tests I serialize and de-serialize my model, parse AsyncApi schema with this library and extract payload with SerializeV2WithoutReference.
\n
That results in JSON like this:
\n
{\n  \"type\": \"object\",\n  \"required\": [\n    \"testA\",\n  ],\n  \"properties\": {\n    \"testA\": {\n      \"type\": \"string\",\n      \"format\": \"uuid\"\n    },\n    \"testB\": {\n      \"$ref\": \"#/components/schemas/testB\"\n    }\n  }\n}\n
\n
testB is still unresolved so I would need to jump through hoops to actually use this JsonSchema to validate my serialized JSON.
\n
Is there any reason to not serialize completely without references, or some way to do that?
\nBonus questions, could this library go step further than just parsing AsyncApi schema and allow validation capacity same as JsonSchema does?
","upvoteCount":1,"answerCount":1,"acceptedAnswer":{"@type":"Answer","text":"
Ive spent a bit more time on the issue, trying to streamline this a bit for the payload schemas.
\nAnyway.. I will make a PR that fixes this.
\n
With default settings you will get an output like this
\n
channels:\n  mychannel:\n    publish:\n      message:\n        payload:\n          type: object\n          required:\n            - testB\n          properties:\n            testC:\n              $ref: '#/components/schemas/testC'\n            testB:\n              $ref: '#/components/schemas/testB'\ncomponents:\n  schemas:\n    testD:\n      type: string\n      format: uuid\n    testC:\n      type: object\n      properties:\n        testD:\n          $ref: '#/components/schemas/testD'\n    testB:\n      type: boolean\n      description: test
\n
But if you instead use the inlinereferences setting
\n
like so
\n
var outputString = new StringWriter(CultureInfo.InvariantCulture);\nvar writer = new AsyncApiYamlWriter(outputString, new AsyncApiWriterSettings { ReferenceInline = ReferenceInlineSetting.InlineReferences });\nasyncApiDocument.SerializeV2(writer);
\n
you will get an output like the following
\n
channels:\n  mychannel:\n    publish:\n      message:\n        payload:\n          type: object\n          required:\n            - testB\n          properties:\n            testC:\n              type: object\n              properties:\n                testD:\n                  type: string\n                  format: uuid\n            testB:\n              type: boolean\n              description: test\ncomponents: { }
","upvoteCount":1,"url":"https://github.com/LEGO/AsyncAPI.NET/discussions/93#discussioncomment-5074289"}}}