in general correct, waiting for the last edits
Still if it's the server doing it, it doesn't resolve my question it's more of a yes or no to my question, followed by a new security issue in case of yes
These queries are a disaster; could grouping be used instead of nesting queries? (At least for counting and sorting.) Also, instead of recalculating the queries every time, couldn't they be…
it could be a public static property from the same paged class, unless you plan to have a config for that too
Need the other comments to be resolved before merge
Can we have a single const with the max PageSize, instead of using magic numbers
Are we sure to enable search queries to non users?
We could extend page size to 1000 rows if the row doesn't weight too much
Are we sure to enable search queries to non users?
It was structured to be possible to search other user, but yet again we need a defined use cases of what we want to actually do
Given that we don't have setting that need to be set before the launch of the service, we can just take the first registration and set it up as admin
Because DateTime happens at the return, it can be directly generated from the caller of the method instead of being made every time, even if you may not care about the time.
The search may be long with a big list of jobs running; it could be favorable to use parallel access to the data structure.
headers should only be used for metadata around a request working, not as actual parameters for a query, if it is needed to handle a starting time, it should be passed as part of a DTO.