Skip to content

V14: Additional blueprint endpoints#16047

Merged
Zeegaan merged 11 commits intov14/devfrom
v14/feature/additional-blueprint-endpoints
Apr 15, 2024
Merged

V14: Additional blueprint endpoints#16047
Zeegaan merged 11 commits intov14/devfrom
v14/feature/additional-blueprint-endpoints

Conversation

@elit0451
Copy link
Contributor

@elit0451 elit0451 commented Apr 12, 2024

Details

  • Fixed /item endpoint to return 0 items when no items' keys are passed in, as opposed to returning all items (there is a task to align this behaviour across all item endpoints);
  • Added 2 new blueprint endpoints:
    • GET /umbraco/management/api/v1/tree/document-blueprint/ancestors - used for breadcrumbs.
    • GET /umbraco/management/api/v1/document-type/{id}/blueprint - used when creating new content, to show the blueprints available for a document type.
  • Fixed some test cases + added some more;

Test

  • Create some blueprints;
  • Test the 3 endpoints:
    • Make sure that you can get the items you expect through the /item endpoint and that you get 0 items when no keys are passed;
    • Pass the blueprint key to the /ancestors endpoint and verify that you get the folder and the item in response;
    • After you have created several blueprints for a /document-type, see if you get the correct items through the document type endpoint.

@elit0451 elit0451 marked this pull request as ready for review April 15, 2024 06:57
Copy link
Member

@Zeegaan Zeegaan left a comment

Choose a reason for hiding this comment

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

Found 2 small things, rest looks good 🚀

Co-authored-by: Nikolaj Geisle <70372949+Zeegaan@users.noreply.github.com>
@Zeegaan Zeegaan merged commit 3edc783 into v14/dev Apr 15, 2024
@Zeegaan Zeegaan deleted the v14/feature/additional-blueprint-endpoints branch April 15, 2024 11:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants