Fix 3803. Added support for oneOf and anyOf for Example Value

[PavelStefanov]

Motivation and Context

Fixes #3803

Description

I added support for oneOf and anyOf attributes for example value tab.

If we have this scheme

/users:
    post:
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                oneOf:
                  - $ref: '#/components/schemas/Jessica'
                  - $ref: '#/components/schemas/Ron'
                  - $ref: '#/components/schemas/dddddd'
                  - type: object
                    properties:
                      id:
                        type: integer
                        format: int64
                      name:
                        type: string

So it will look like this

Each subscheme will be rendered with name and in separate highlight block.
I'll be glad to your ideas and comments!

How Has This Been Tested?

I tested different cases of oneOf and anyOf, but I'm not sure I was able to cover all cases.

My PR contains...

• No code changes (src/ is unmodified: changes to documentation, CI, metadata, etc.)
• Dependency changes (any modification to dependencies in package.json)
• Bug fixes (non-breaking change which fixes an issue)
• Improvements (misc. changes to existing features)
• Features (non-breaking change which adds functionality)

My changes...

• are breaking changes to a public API (config options, System API, major UI change, etc).
• are breaking changes to a private API (Redux, component props, utility functions, etc.).
• are breaking changes to a developer API (npm script behavior changes, new dev system dependencies, etc).
• are not breaking changes.

Documentation

• My changes do not require a change to the project documentation.
• My changes require a change to the project documentation.
• If yes to above: I have updated the documentation accordingly.

Automated tests

• My changes can not or do not need to be tested.
• My changes can and should be tested by unit and/or integration tests.
• If yes to above: I have added tests to cover my changes.
• If yes to above: I have taken care to cover edge cases in my tests.
• All new and existing tests passed.

[heldersepu]

No UnitTests?

[shockey]

I like the functionality, but this PR needs tests 😄

[shockey]

@webron, could use your take on the visual changes

[alvarolb]

Nice feature!

It would be great to have this also on requests. Not sure if it is so complex, but It will be great if instead of showing all possible cases, just place a select control to select one of the possible cases.

Best.

[PavelStefanov]

@heldersepu @shockey thx guys, on these weekends I'll try add unit tests

[webron]

@PavelStefanov Thanks for the PR and sorry for the delay in reviewing it. I have a few comments, but they are all also related to dealing with the bigger issue at hand. I'll take the discussion back to #3803 to get more interaction from the community at large.

[shockey]

closing due to inactivity!