swagger-api / swagger-api/swagger-ui

JSON Schema Draft 4/5 extension rendering

Open
#9,377 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type: feature version: 5.x
Dominant language
JavaScript
Stars
29k
Forks
9.3k
Avg merge
2d 23h
Merged PRs (30d)
25

Description

To have more flexibility let's extract the react code handling rendering of the spec extensions into separate overridable component. When we have that, the API consumer will be able to override how the extensions to Schema Object render depending on their name.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the React code that renders Schema Object extensions. Extract that rendering into a separate overridable component, then verify that an API consumer can customize rendering based on each extension's name.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, react
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.