-
Notifications
You must be signed in to change notification settings - Fork 1k
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
[24.0] Fix histories API index_query serialization #17726
[24.0] Fix histories API index_query serialization #17726
Conversation
Nice find! Could you add an API test that makes sure we're not getting the detailed view when requesting the summary ? |
a93a2a9
to
dc6c47e
Compare
2bd2dc1
to
1cd3241
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.
looks good, thanks!
the test fails are likely related though
|
Thanks! Investigating... 🔎 |
There seems to be some black magic at play here... This is the effect of 1cd3241 but all responses seem completely fine at first sight and no trace of error anywhere. I'll investigate what the MultiHistory View is doing or expecting regarding this... |
Definitely nothing wrong with 1cd3241. I will drop 1cd3241 from here since it is not really related to the serialization problem and open a follow-up PR including that change and addressing the issue in the client. |
For consistency with the existing history index action.
In both modes
1cd3241
to
216036c
Compare
Until the HistoryMinimal model gets replaced by the CustomHistory again.
we should follow up with taking HistoryDetailed but making everything optional again, like we discussed in the backend channel some time ago. |
Right! Thanks for remembering, I had already forgot 😅 |
I'll see what I can do to fix it. |
It seems to be related to when requesting only specific keys the UpdateI thought the request was failing because of this, but the failure was me trying to work on 2 things at the same time and mixing branches 🤦 The test failed because it was expecting the username to be present in the listing and that was not part of the summary view as hinted in Marius' screenshot. I need a break 😅 |
Tests are passing now. The failing Toolshed one is unrelated. |
Follow up to #17717
Fixes #17723
The alternative "index_query" was missing the "serialization_params".
It also adds the "summary" view to the rest of the History Grid listings and it makes this the default serialization view for histories retrieved in "query" mode for consistency with the original "index" endpoint.
Hopefully this time it should make a little difference.
How to test the changes?
License