Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Clarify endpoint documentation #138

Closed
derrickmehaffy opened this issue Feb 19, 2021 · 0 comments
Closed

Clarify endpoint documentation #138

derrickmehaffy opened this issue Feb 19, 2021 · 0 comments
Assignees
@pwizla
Labels
internal PRs created by the Strapi core team pr: fix Used on the docs repo for anything that is not "new" or "updated" content: chore, typos, fixes, etc. source: Dev Docs PRs/issues targeting the Developer Docs status: confirmed Confirmed by a Strapi Team member or multiple community members target: v3 Documentation PRs/issues targeting content from docs-v3.strapi.io (v3 branch)

Comments

@derrickmehaffy
Copy link
Member

Per a user on slack, the following documentation: https://strapi.io/documentation/developer-docs/latest/content-api/api-endpoints.html#update-an-entry is not quite clear if the content/open hours are relations or components.

As we don't support nested relational POST/PUT request, we should clarify this documentation to show those are components.
@derrickmehaffy derrickmehaffy added source: Dev Docs PRs/issues targeting the Developer Docs status: confirmed Confirmed by a Strapi Team member or multiple community members pr: fix Used on the docs repo for anything that is not "new" or "updated" content: chore, typos, fixes, etc. labels Feb 19, 2021
@pwizla pwizla self-assigned this Mar 5, 2021
@pwizla pwizla added target: v3 Documentation PRs/issues targeting content from docs-v3.strapi.io (v3 branch) internal PRs created by the Strapi core team labels May 16, 2022
@pwizla pwizla closed this as completed May 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pwizla pwizla

Labels
internal PRs created by the Strapi core team pr: fix Used on the docs repo for anything that is not "new" or "updated" content: chore, typos, fixes, etc. source: Dev Docs PRs/issues targeting the Developer Docs status: confirmed Confirmed by a Strapi Team member or multiple community members target: v3 Documentation PRs/issues targeting content from docs-v3.strapi.io (v3 branch)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pwizla @derrickmehaffy