Skip to content

fix: Invalid Parameters handling in Planning History API #260#276

Open
codecharlan wants to merge 1 commit intotoloka-agent/128-autofrom
bugfix/260-invalid-parameters-handling-in-planning-history-api
Open

fix: Invalid Parameters handling in Planning History API #260#276
codecharlan wants to merge 1 commit intotoloka-agent/128-autofrom
bugfix/260-invalid-parameters-handling-in-planning-history-api

Conversation

@codecharlan
Copy link
Copy Markdown

@codecharlan codecharlan commented Mar 21, 2026

Bug fix for #260

FAIL_TO_PASS: PlanningHistoryControllerTests#shouldReturn400ForInvalidChangeType, PlanningHistoryControllerTests#shouldReturn400ForInvalidEntityType, PlanningHistoryControllerTests#shouldReturn400ForInvalidDateFormat, PlanningHistoryControllerTests#shouldReturn400ForInvalidPageNumber, PlanningHistoryControllerTests#shouldReturn400ForInvalidPageSize, PlanningHistoryControllerTests#shouldReturn400ForInvalidSortParameter

@codecharlan codecharlan force-pushed the bugfix/260-invalid-parameters-handling-in-planning-history-api branch from 21a44c7 to b825105 Compare March 25, 2026 17:48
@codecharlan codecharlan force-pushed the bugfix/260-invalid-parameters-handling-in-planning-history-api branch from b825105 to 0be46ac Compare March 25, 2026 18:11
@github-actions github-actions bot added Verified and removed Review labels Mar 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants