-
-
Notifications
You must be signed in to change notification settings - Fork 555
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
XWIKI-20632: Page searched by its exact name is not found in a page picker for a macro parameter when its subtree is larger than 10 pages #2945
Conversation
…icker for a macro parameter when its subtree is larger than 10 pages * Search only in the actual page name, not in the space hierarchy.
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.
Small note but there's no unit test for this class?
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.
No, there do not seem to be any unit tests for this class.
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.
lgtm modulo missing tests. No sure exactly what best to test. Testing the well-formedness of the queries is an easy first step. Then, I wonder if a functional test covering this case is interesting.
…icker for a macro parameter when its subtree is larger than 10 pages * Add tests.
I have added two integration tests now: one on the level of the REST API, and another for the page picker. I ran
Both passed. |
…icker for a macro parameter when its subtree is larger than 10 pages * Reduce the number of pages created in the test.
Jira URL
https://jira.xwiki.org/browse/XWIKI-20632
Changes
Description
Clarifications
Screenshots & Video
No UI change except that the search results are different now.
Executed Tests
Manually tested the change, still need to see if we have any existing tests.
Expected merging strategy