Support fetchOrientation parameter in OperationRestApi.getOperationLog #7428
Closed
ychris78 wants to merge 3 commits into
Closed
Support fetchOrientation parameter in OperationRestApi.getOperationLog #7428ychris78 wants to merge 3 commits into
ychris78 wants to merge 3 commits into
Conversation
added 2 commits
May 2, 2026 10:32
pan3793
approved these changes
May 4, 2026
Member
|
thanks, merged to master |
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
2 participants
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.
Why are the changes needed?
The current getOperationLog method in OperationRestApi does not support the fetchOrientation parameter, which limits the client's ability to control the fetch direction (e.g., FETCH_NEXT, FETCH_FIRST) when retrieving operation logs. This change adds an overloaded method that accepts
fetchOrientation, while keeping the original method signature for backward compatibility.
How was this patch tested?
Was this patch authored or co-authored using generative AI tooling?
No