2015-01-27 11:10:29 +01:00
|
|
|
node_modules
|
2016-06-18 09:19:57 +02:00
|
|
|
lerna-debug
|
|
|
|
|
npm-debug
|
2015-01-27 11:10:29 +01:00
|
|
|
.DS_Store
|
2021-02-12 11:42:00 +01:00
|
|
|
/dist
|
2015-01-27 11:10:29 +01:00
|
|
|
|
2014-09-29 14:50:46 +02:00
|
|
|
# Logs
|
|
|
|
|
logs
|
|
|
|
|
*.log
|
|
|
|
|
|
|
|
|
|
# Runtime data
|
|
|
|
|
pids
|
|
|
|
|
*.pid
|
|
|
|
|
*.seed
|
|
|
|
|
|
|
|
|
|
# Directory for instrumented libs generated by jscoverage/JSCover
|
|
|
|
|
lib-cov
|
|
|
|
|
|
|
|
|
|
# Coverage directory used by tools like istanbul
|
2022-05-20 11:14:41 +02:00
|
|
|
# coverage
|
2022-05-20 19:29:14 +02:00
|
|
|
coverage/lcov-report
|
2014-09-29 14:50:46 +02:00
|
|
|
|
|
|
|
|
# Compiled binary addons (http://nodejs.org/api/addons.html)
|
|
|
|
|
build/Release
|
|
|
|
|
|
2014-10-31 16:35:35 +01:00
|
|
|
# liquibase stuff
|
|
|
|
|
/sql
|
|
|
|
|
unleash-db.jar
|
2014-11-01 11:47:21 +01:00
|
|
|
unleash-server.tar.gz
|
|
|
|
|
|
|
|
|
|
# idea stuff:
|
2016-05-03 12:12:37 +02:00
|
|
|
.idea/*
|
2015-06-19 14:11:02 +02:00
|
|
|
|
|
|
|
|
.vagrant/
|
2016-04-30 10:47:17 +02:00
|
|
|
|
|
|
|
|
# Visual Studio Code
|
|
|
|
|
jsconfig.json
|
2016-04-30 22:11:16 +02:00
|
|
|
typings
|
2016-11-13 15:41:35 +01:00
|
|
|
.nyc_output
|
2017-11-04 12:09:12 +01:00
|
|
|
|
|
|
|
|
# We use yarn.lock
|
|
|
|
|
package-lock.json
|
2018-11-20 20:34:42 +01:00
|
|
|
|
|
|
|
|
# Website stuff
|
|
|
|
|
/website/build
|
|
|
|
|
/website/backers.json
|
|
|
|
|
/website/node_modules
|
|
|
|
|
/website/translated_docs
|
2021-10-12 10:39:28 +02:00
|
|
|
/website/i18n/*
|
|
|
|
|
.env
|
|
|
|
|
|
2023-04-18 15:44:19 +02:00
|
|
|
# Ignore frontend build
|
|
|
|
|
frontend/build
|
docs: auto-generate remaining server-side SDK docs (#2858)
This PR builds on the preceding doc auto-generation PRs and generates
documentation for the remaining server-side SDKs.
## Why
Refer to https://github.com/Unleash/unleash/pull/2809 for more context
about generating SDK docs.
## What
- Adds generation for the remaining server-side SDKs
- Moves generated docs from the `/reference/sdks` directory to
`/generated` directory.
- Makes sure that the URLs do not change because of the move by using
the `slug` frontmatter property.
- replaces relative github links in the markdown documents so that they
become absolute github links. (refer to the next section)
- Updates some image styling so that it doesn't apply to readme badges
(we don't need them using `display: block`)
### On link replacing:
This PR adds handling of links in the generated documentation.
Specifically, it changes links in one case:
Relative links to github. Links to code and other files in the
repository. These are prefixed with the repository's URL.
While this should work in most cases, it will fail in cases where the
links to the files are not on the repository's primary branch.
(typically main, but could also be "v3", for instance). In these cases,
the links will get a double branch in the URL and will fail. However, I
see no easy way around this (though suggestions are definitely
accepted!), and think it's a fair tradeoff. It takes the links from
"definitely failing" to "will work in the vast majority of cases".
Note: I originally also wanted to handle the case where the link is an
absolute link to docs.getunleash.io. We could turn these into relative
urls to avoid full page reloads and enjoy a smoother experience.
However, the client-side redirects don't work correctly if the relative
URL goes to a redirect page, so you end up with a 404 page. As such, I
think it's better to leave the links as absolute for now.
2023-01-13 12:40:28 +01:00
|
|
|
|
2023-10-02 12:35:20 +02:00
|
|
|
# Ignore orval apis
|
|
|
|
|
frontend/src/openapi/apis
|
2023-10-18 08:55:07 +02:00
|
|
|
frontend/src/openapi/index.ts
|
2023-10-02 12:35:20 +02:00
|
|
|
|
docs: auto-generate remaining server-side SDK docs (#2858)
This PR builds on the preceding doc auto-generation PRs and generates
documentation for the remaining server-side SDKs.
## Why
Refer to https://github.com/Unleash/unleash/pull/2809 for more context
about generating SDK docs.
## What
- Adds generation for the remaining server-side SDKs
- Moves generated docs from the `/reference/sdks` directory to
`/generated` directory.
- Makes sure that the URLs do not change because of the move by using
the `slug` frontmatter property.
- replaces relative github links in the markdown documents so that they
become absolute github links. (refer to the next section)
- Updates some image styling so that it doesn't apply to readme badges
(we don't need them using `display: block`)
### On link replacing:
This PR adds handling of links in the generated documentation.
Specifically, it changes links in one case:
Relative links to github. Links to code and other files in the
repository. These are prefixed with the repository's URL.
While this should work in most cases, it will fail in cases where the
links to the files are not on the repository's primary branch.
(typically main, but could also be "v3", for instance). In these cases,
the links will get a double branch in the URL and will fail. However, I
see no easy way around this (though suggestions are definitely
accepted!), and think it's a fair tradeoff. It takes the links from
"definitely failing" to "will work in the vast majority of cases".
Note: I originally also wanted to handle the case where the link is an
absolute link to docs.getunleash.io. We could turn these into relative
urls to avoid full page reloads and enjoy a smoother experience.
However, the client-side redirects don't work correctly if the relative
URL goes to a redirect page, so you end up with a 404 page. As such, I
think it's better to leave the links as absolute for now.
2023-01-13 12:40:28 +01:00
|
|
|
# Generated docs
|
|
|
|
|
website/docs/reference/api/**/sidebar.js
|
2023-07-10 16:28:34 +02:00
|
|
|
website/docs/reference/api/**/**.info.mdx
|
docs: auto-generate remaining server-side SDK docs (#2858)
This PR builds on the preceding doc auto-generation PRs and generates
documentation for the remaining server-side SDKs.
## Why
Refer to https://github.com/Unleash/unleash/pull/2809 for more context
about generating SDK docs.
## What
- Adds generation for the remaining server-side SDKs
- Moves generated docs from the `/reference/sdks` directory to
`/generated` directory.
- Makes sure that the URLs do not change because of the move by using
the `slug` frontmatter property.
- replaces relative github links in the markdown documents so that they
become absolute github links. (refer to the next section)
- Updates some image styling so that it doesn't apply to readme badges
(we don't need them using `display: block`)
### On link replacing:
This PR adds handling of links in the generated documentation.
Specifically, it changes links in one case:
Relative links to github. Links to code and other files in the
repository. These are prefixed with the repository's URL.
While this should work in most cases, it will fail in cases where the
links to the files are not on the repository's primary branch.
(typically main, but could also be "v3", for instance). In these cases,
the links will get a double branch in the URL and will fail. However, I
see no easy way around this (though suggestions are definitely
accepted!), and think it's a fair tradeoff. It takes the links from
"definitely failing" to "will work in the vast majority of cases".
Note: I originally also wanted to handle the case where the link is an
absolute link to docs.getunleash.io. We could turn these into relative
urls to avoid full page reloads and enjoy a smoother experience.
However, the client-side redirects don't work correctly if the relative
URL goes to a redirect page, so you end up with a 404 page. As such, I
think it's better to leave the links as absolute for now.
2023-01-13 12:40:28 +01:00
|
|
|
website/docs/generated
|
2023-05-25 13:03:54 +02:00
|
|
|
reports/jest-junit.xml
|
