Skip to content

Conversation

@adriendupuis
Copy link
Contributor

@adriendupuis adriendupuis commented May 11, 2022

Question Answer
JIRA Ticket IBX-1430
Versions 4.1, 4.0

Fix several indentation errors that hide some parts or create non-existing routes.

  • /calendar/calendar/event/calendar/event
  • /commerce/basket/{basketId}/{basketId}/line/commerce/basket/{basketId}/line
  • /content/assets/assets/images/content/assets/images
  • /content/locations/{path}/{locationId}/content/locations/{path} (the two forms were existing and are now merged; the first one is not necessary as the location ID is always part of the location path.)
  • /content/locations/{path}/children and /content/locations/{path}/urlaliases were absent from HTML output.
  • /content/objects's POST request example was badly indented.
  • /content/objectstategroups/objectstates/content/objectstategroups/{objectStateGroupId}/objectstates
  • /content/types/{contentTypeId}/{fieldDefinitionId}/content/types/{contentTypeId}/fielddefinitions/{fieldDefinitionId}
  • remove non-existing /content/views/{identifier} (/views/{viewId} equivalent is not implemented)
  • /product/catalog/attributes/{id}'s request body example was absent from HTML output.
  • /product/catalog/attributes/translation/{languageCode}/product/catalog/attributes/translation/{id}/{languageCode}
  • /product/catalog/attribute_groups's 403 descriptions were incomplete or erroneous.
  • /user/users:

@adriendupuis
Copy link
Contributor Author

I found the missing /content/locations/{path}/urlaliases documentation during #1591. There is certainly more.

TODO: Found other wrongly indented sub-resources.

@adriendupuis adriendupuis changed the title IBX-1430: Fix REST API reference parts which do not appear IBX-1430: Fix REST API reference absent parts May 11, 2022
@adriendupuis adriendupuis changed the title IBX-1430: Fix REST API reference absent parts IBX-1430: Revise REST API reference May 16, 2022
- Fix indentation
- Same self-closing tag format
string(150) "application/vnd.ibexa.api.AttributeGet+json type: AttributeList example: !include examples/product/catalog/attributes/id/GET/AttributeGet.json.example"
PHP Warning:  Invalid argument supplied for foreach() in /Users/adriendupuis/www/developer-documentation/tools/raml2html/vendor/raml-org/raml-php-parser/src/Method.php on line 147
@adriendupuis adriendupuis changed the title IBX-1430: Revise REST API reference IBX-1430: Fix REST API reference Jun 7, 2022
…dent

/content/objectstategroups/objectstates doesn't exist; /content/objectstategroups/{objectStateGroupId}/objectstates does: https://github.com/ibexa/rest/blob/v4.0.0/src/bundle/Resources/config/routing.yml#L326
…indent

/content/types/{contenttypeid}/{fielddefinitionid} doesn't exist; /content/types/{contenttypeid}/fielddefinitions/{fielddefinitionid} does: https://github.com/ibexa/rest/blob/v4.0.0/src/bundle/Resources/config/routing.yml#L578
/content/assets/assets/images/{assetId}/{assetSource} doesn't exist; only /content/assets/images/{assetId}/{assetSource}: https://github.com/ibexa/connector-dam/blob/v4.0.0/src/bundle/Resources/config/routing_rest.yaml#L9

/calendar/calendar/event doesn't exists; only /calendar/event: https://github.com/ibexa/calendar/blob/main/src/bundle/Resources/config/routing_rest.yaml
/commerce/basket/{basketId}/{basketId}/line doesn't exist while /commerce/basket/{basketId}/line does at https://github.com/ibexa/commerce-rest/blob/v4.0.0/src/bundle/Resources/config/routing.yaml#L67

/commerce/basket/{basketId}/{basketId}/line/{lineId} doesn't exist while /commerce/basket/{basketId}/line/{lineId} does at https://github.com/ibexa/commerce-rest/blob/v4.0.0/src/bundle/Resources/config/routing.yaml#L87
…tion/{languageCode}

/product/catalog/attributes/translation/{languageCode} doesn't exist while /product/catalog/attributes/translation/{identifier}/{languageCode} exists in https://github.com/ibexa/product-catalog/blob/v4.0.0/src/bundle/Resources/config/routing_rest.yaml#L69
Same format than in `/product/catalog/attribute_groups/translation/{id}/{languageCode}`
@adriendupuis adriendupuis marked this pull request as ready for review June 8, 2022 10:33
@adriendupuis adriendupuis requested a review from DominikaK June 8, 2022 10:33
@DominikaK DominikaK self-assigned this Jun 8, 2022
@adriendupuis adriendupuis merged commit 7544e68 into master Jun 8, 2022
@adriendupuis adriendupuis deleted the fix/rest-api-reference branch June 8, 2022 13:45
adriendupuis added a commit that referenced this pull request Jun 8, 2022
This is the tool that helped a lot on #1615 to test what was already in the reference and that will help to found missing entries.
adriendupuis added a commit that referenced this pull request Jun 9, 2022
- Fix several indentation errors that hide some parts or create non-existing routes.
- Fix /user/users parameters

(cherry picked from commit 7544e68)
adriendupuis added a commit that referenced this pull request Jun 9, 2022
- Fix several indentation errors that hide some parts or create non-existing routes.
- Fix /user/users parameters

(cherry picked from commit 7544e68)
queryParameters:
roleId:
description: Lists User Groups assigned to the given Role.
description: Lists User Groups assigned to the given Role (e.g. GET /user/users?roleId=/user/roles/1).
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be /user/groups?roleId=/user/roles/1 💩

description: Checks if there are Users directly assigned to the given Role.
remoteId:
description: Retrieves the User for the given remote ID (e.g. GET /user/users?remoteId=55dd9713db75145f374bbd0b4f60ad29).
description: Checks if there is a User for the given remote ID (e.g. GET /user/users?remoteId=55dd9713db75145f374bbd0b4f60ad29).
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the examples, it should be HEAD instead of GET

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants