improve postman workflow tests#35729
Draft
dario-daza wants to merge 6 commits into
Draft
Conversation
Contributor
This file contains hidden or 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
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.
Proposed Changes
GET /api/v1/workflow/schemes/schemes-content-typesendpoint (findAllSchemesByContentTypeList) that accepts a comma-separatedcontentTypeIdsquery parameter and returns workflow schemes grouped by content typeAbstractContentTypeWorkflowSchemesView(Immutables) withcontentTypeId+contentTypeSchemesfields, andResponseEntityContentTypeWorkflowSchemesViewas the typed response wrappercontentTypeIdscomma-separated values (?contentTypeIds=id1,id2,id3) rather than repeated params — trims whitespace and filters empty tokensWorkflowResourceResponseCodeIntegrationTestcovering: null input, empty string, whitespace-only tokens, IDs with surrounding whitespace, invalid ID (expects 404), happy path with comma-separated valid IDs, and documented repeated-param limitationAdditional Info
The endpoint returns a structured
List<{contentTypeId, contentTypeSchemes[]}>rather than a flat deduplicated list - this keeps the association between each content type and its schemes intact and lets the frontend handle deduplication if needed.This PR fixes: #35471