Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
This repository was archived by the owner on Dec 7, 2022. It is now read-only.
/ReDocPublic archive
forked fromRedocly/redoc

📘 OpenAPI/Swagger-generated API Reference Documentation

License

NotificationsYou must be signed in to change notification settings

litmusautomation/ReDoc

 
 

Repository files navigation

ReDoc logo

OpenAPI/Swagger-generated API Reference Documentation

Build StatusCoverage StatusTested on APIs.gurudependencies StatusdevDependencies StatusStories in Ready

Average time to resolve an issuePercentage of issues still open

npmLicense

Browser Compatibility

ReDoc demo

Deploy to GithubReDoc as a serviceCustomization services

Features

  • Extremely easy deployment
  • The widest OpenAPI v2.0 features support (yes, it supports evendiscriminator)
  • Neatinteractive documentation for nested objects
  • Code samples support (via vendor extension)
  • Progressive loading withlazy-rendering options
  • Responsive three-panel design with menu/scrolling synchronization
  • Integrate API Introduction into side menu - ReDoc takes advantage of markdown headings from OpenAPI description field. It pulls them into side menu and also supports deep linking.
  • High-level grouping in side-menu viax-tagGroups vendor extension
  • Multiple ReDoc instances on single page (example)

Roadmap

  • OpenAPI v3.0 support
  • performance optimizations
  • better navigation (menu improvements + search)
  • ability to simple branding/styling
  • built-in API Console
  • docs pre-rendering (performance and SEO)

Releases

We host the latest and all the previous ReDoc releases on GitHub Pages-basedCDN:

Version Guidance

ReDoc ReleaseOpenAPI Specification
1.19.x2.0
1.18.x2.0
1.17.x2.0

Some Real-life usages

Deployment

TL;DR

<!DOCTYPE html><html><head><title>ReDoc</title><!-- needed for adaptive design --><metacharset="utf-8"/><metaname="viewport"content="width=device-width, initial-scale=1"><!--    ReDoc doesn't change outer page styles    --><style>body {margin:0;padding:0;      }</style></head><body><redocspec-url='http://petstore.swagger.io/v2/swagger.json'></redoc><scriptsrc="https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js"></script></body></html>

That's all folks!

IMPORTANT NOTE: if you work with untrusted user spec, useuntrusted-specoption to prevent XSS security risks.

1. Install ReDoc (skip this step for CDN)

Install usingyarn:

yarn add redoc

or usingnpm:

npm install redoc --save

2. Reference redoc script in HTML

ForCDN:

<scriptsrc="https://rebilly.github.io/ReDoc/releases/latest/redoc.min.js"></script>

For npm:

<scriptsrc="node_modules/redoc/dist/redoc.min.js"></script>

3. Add<redoc> element to your page

<redocspec-url="url/to/your/spec"></redoc>

4. Enjoy 😄

Configuration

Security Definition location

You can inject Security Definitions widget into any place of your specificationdescription. Check out detailshere.

Swagger vendor extensions

ReDoc makes use of the followingvendor extensions:

  • x-logo - is used to specify API logo
  • x-traitTag - useful for handling out common things like Pagination, Rate-Limits, etc
  • x-code-samples - specify operation code samples
  • x-examples - specify JSON example for requests
  • x-nullable - mark schema param as a nullable
  • x-displayName - specify human-friendly names for the menu categories
  • x-tagGroups - group tags by categories in the side menu
  • x-servers - ability to specify different servers for API (backported from OpenAPI 3.0)
  • x-ignoredHeaderParameters - ability to specify header parameter names to ignore

<redoc> tag attributes

  • spec-url - relative or absolute url to your spec file;
  • untrusted-spec - if set, the spec is considered untrusted and all HTML/markdown is sanitized to prevent XSS.Disabled by default for performance reasons.Enable this option if you work with untrusted user data!
  • scroll-y-offset - If set, specifies a vertical scroll-offset. This is often useful when there are fixed positioned elements at the top of the page, such as navbars, headers etc;scroll-y-offset can be specified in various ways:
    • number: A fixed number of pixels to be used as offset;
    • selector: selector of the element to be used for specifying the offset. The distance from the top of the page to the element's bottom will be used as offset;
    • function: A getter function. Must return a number representing the offset (in pixels);
  • suppress-warnings - if set, warnings are not rendered at the top of documentation (they still are logged to the console).
  • lazy-rendering - if set, enables lazy rendering mode in ReDoc. This mode is useful for APIs with big number of operations (e.g. > 50). In this mode ReDoc shows initial screen ASAP and then renders the rest operations asynchronously while showing progress bar on the top. Check out thedemo for the example.
  • hide-hostname - if set, the protocol and hostname is not shown in the operation definition.
  • hide-download-button - do not show "Download" spec button.THIS DOESN'T MAKE YOUR SPEC PRIVATE, it just hides the button.
  • expand-responses - specify which responses to expand by default by response codes. Values should be passed as comma-separated list without spaces e.g.expand-responses="200,201". Special value"all" expands all responses by default. Be careful: this option can slow-down documentation rendering time.
  • required-props-first - show required properties first ordered in the same order as inrequired array.
  • no-auto-auth - do not inject Authentication section automatically
  • path-in-middle-panel - show path link and HTTP verb in the middle panel instead of the right one
  • hide-loading - do not show loading animation. Useful for small docs
  • native-scrollbars - use native scrollbar for sidemenu instead of perfect-scroll (scrolling performance optimization for big specs)

Advanced usage

Instead of addingspec-url attribute to the<redoc> element you can initialize ReDoc via globally exposedRedoc object:

Redoc.init(specOrSpecUrl,options)

specOrSpecUrl is either JSON object with specification or an URL to the spec inJSON orYAML format.options is javascript object with camel-cased version of<redoc> tag attribute names as the keys, e.g.:

Redoc.init('http://petstore.swagger.io/v2/swagger.json',{scrollYOffset:50})

Development

Running local dev-server

  • Clone repositorygit clone https://github.com/Rebilly/ReDoc.git
  • Go to the project foldercd ReDoc
  • Install dependenciesnpm install
  • (optional) Replacedemo/swagger.yaml with your own schema
  • Start the servernpm start
  • Openhttp://localhost:9000

Alternatively, Docker can be used by just runningdocker-compose up.

About

📘 OpenAPI/Swagger-generated API Reference Documentation

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • TypeScript70.1%
  • CSS14.7%
  • JavaScript8.1%
  • HTML7.1%

[8]ページ先頭

©2009-2025 Movatter.jp