-
Notifications
You must be signed in to change notification settings - Fork 269
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
[ACA-3672] - added server order for document -list #5899
Conversation
Vito Albano seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
Codecov Report
@@ Coverage Diff @@
## develop #5899 +/- ##
===========================================
+ Coverage 76.24% 76.53% +0.28%
===========================================
Files 839 830 -9
Lines 18632 18384 -248
Branches 3656 3590 -66
===========================================
- Hits 14206 14070 -136
+ Misses 3318 3218 -100
+ Partials 1108 1096 -12
Continue to review full report at Codecov.
|
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.
can you also regenerate the doc with npm run docbuild?
} | ||
} | ||
|
||
private retrieveDocumentNode(nodeId: string, pagination: PaginationModel, includeFields: string[], where?: string): Observable<DocumentLoaderNode> { | ||
private retrieveDocumentNode(nodeId: string, pagination: PaginationModel, includeFields: string[], where?: string, orderByValue?: string[]): Observable<DocumentLoaderNode> { |
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.
orderByValue can we rename it to orderBy ?
4080d3d
to
5cb64a8
Compare
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x")
What is the current behaviour? (You can also link to an open issue here)
Document list apply only FE sorting
What is the new behaviour?
Document list apply FE or BE sorting
Does this PR introduce a breaking change? (check one with "x")
If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:
https://issues.alfresco.com/jira/browse/ACA-3672