mirror of
https://github.com/Unleash/unleash.git
synced 2024-12-22 19:07:54 +01:00
6b4efb9a9d
https://linear.app/unleash/issue/2-943/adr-separate-request-and-response-types-in-apis During the updating of our OpenAPI documentation, we've seen several times that our schemas are either way too wide for a response or way to strict for a request. This is usually due to us reusing the same schema for both request and response. We should write an ADR where we reason about the usefulness of code duplication and keeping separate response and request schemas. Based on our needs, this PR adds my suggested ADR. --------- Co-authored-by: Simon Hornby <liquidwicked64@gmail.com> |
||
---|---|---|
.. | ||
.storybook | ||
docs | ||
remote-content | ||
src | ||
static | ||
.gitignore | ||
babel.config.js | ||
clean-generated-docs.js | ||
docusaurus.config.js | ||
package.json | ||
README.md | ||
sidebars.js | ||
tsconfig.json | ||
yarn.lock |
Website
This website is built using Docusaurus 2, a modern static website generator.
Installation
yarn install
Local Development
yarn start
This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.
Build
yarn build
This command generates static content into the build
directory and can be served using any static contents hosting service.
Deployment
GIT_USER=<Your GitHub username> USE_SSH=true yarn deploy
If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the gh-pages
branch.