-
Notifications
You must be signed in to change notification settings - Fork 80
[PROVIDER-2289] fix terminals/status endpoint losing status data when pagination disabled #2997
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.
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
base: main
Are you sure you want to change the base?
[PROVIDER-2289] fix terminals/status endpoint losing status data when pagination disabled #2997
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR is not ready to merge.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please, add an API test to brand getTerminal with _pagination=false to test this.
c417bb1
to
8efb00d
Compare
web/rest/brand/features/provider/terminal/getTerminalStatus.feature
Outdated
Show resolved
Hide resolved
d41e745
to
2f2c96c
Compare
2f2c96c
to
e1b8868
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overriding the default controller has side effects. What happens with filters?
Moreover: what happens with pagination itself?
if you pass _itemsPerPage=1, how many items does this return?
…atus endpoint
Type Of Change
Checklist:
Description
Additional information