Add openapi.json route documentation (#2143) #2159
Open
+11,307
−2,600
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This reverts commit 0a446e0.
Because I tested this example to replace the favicon, and I've got an error.
```bash
yarn run v1.22.19
$ strapi build
⠋ Building build context
[INFO] Including the following ENV variables as part of the JS bundle:
- ADMIN_PATH
- STRAPI_ADMIN_BACKEND_URL
- STRAPI_TELEMETRY_DISABLED
✔ Building build context (73ms)
⠋ Building admin panel
⠴ Building admin panel[ERROR] Module not found: Error: Can't resolve './extensions/favicon.png' in '/var/www/strapi/src/admin'
✖ Building admin panel
[ERROR] There seems to be an unexpected error, try again with --debug for more information
error Command failed with exit code 1.
```
* Document Node version feature in deployment guide * Update advanced settings screenshots
* Rework TOC titles * Separate account/sessing into 2 pages * Start working the Projects section * Rework and complete Usage and Billing page * Rework Projects overview page * Fix links in Usage and Billing * Separate deployment and deploy history in 2 pages and rework content in both * Move deployment pages to a new Deployments section in the TOC * Review Overview and Settings pages * Review or write content for deploys docs and runtime logs * Delete custom plan from Billing & Usage page * Mention GitLab where it was forgotten * Improve Notifications page * Fix/improve all projects management pages * Fix/improve all deployments pages * Fix/improve Account settings page * Update all screenshots * Fix broken links * Fix header link * Remove useless link in Project settings Co-authored-by: Pierre Wizla <[email protected]> * Update one more screenshot + Delete useless comments * Add icons * Delete More.svg in static * Delete more.svg again * Add More.svg * Fix icon name in releases * Add Node version feature in Project settings + Update screenshot * Add forgotten word in deploy logs --------- Co-authored-by: Pierre Wizla <[email protected]> Co-authored-by: Pierre Wizla <[email protected]>
* Update account billing page * Update screenshot
* Extend new/updated badges usage outside TOC * Fix "updated" badges usage in TOC * Add badges where appropriate
* feat(cli): strapi projects * Update docusaurus/docs/cloud/cli/cloud-cli.md --------- Co-authored-by: Gonzalo Andres Garcia <[email protected]>
Co-authored-by: Pierre Wizla <[email protected]>
provide more information on setting the role of a newly created user.
This reverts commit 4fedfcd.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
|
This was referenced Jul 29, 2024
pwizla
added
source: Dev Docs
pwizla
requested review from
derrickmehaffy and
meganelacheny
as code owners
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does it do?
Adds documentation for new route
/documentation/<version>/openapi.jsonprovided by the documentation plugin.Preview:
Why is it needed?
This is needed to inform devs that there is a way to access the
full_documentation.jsonvia endpoint of the documentation plugin.Related issue(s)/PR(s)