-
Notifications
You must be signed in to change notification settings - Fork 30
Sort and filter comment replies the same as root comments #1563
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
Conversation
- pass the criteria through to match child comments by it - included criteria: - ordering - banned hashtag checking - preferred languages - federation filter (not used with comments, but still included) - time filter (also not used for comments atm) - filter out comments from banned authors
- bring back the comment hydration. It reduces the number of queries especially on a highly commented post quite a bit. - Use hydration in the `PostSingleController` and the `EntrySingleController` as well - fix the `EntryCommentViewController` which did not pass the criteria parameter
Because we have a bit more complex orderings I switched from the `Criteria::orderBy` which does not support mathematical operations between multiple fields as orderings to `uasort`. This should not come with a performance impact, as the doctrine way also just does a `uasort` for all orderings. I just recreated the ordering from the `EntryCommentRepository::filter` method
- use `hydrateChildren` in the `EntrySingleController` and the `PostSingleController` - use hydration in the `EntryCommentViewController` - add `hydrateChildren` to the `PostCommentRepository`
|
I'm getting this weird error with Docker now. When I try to use I did change the docker image to the main tag: But when running: docker compose up -dI see: Any clue? EDIT: Let me try to comment out the Nope.. same issue: |
|
As far as I know it is the autoloader generated by composer that fucked up... So rerun |
This is what the script should do by default in docker. Right @jwr1? It seems we missed something with the docker setup. |
|
I thought that that fixed it for me locally when I was developing (also with docker)... Not sure how I fixed it if it was not with these commands... |
Closes #1397