| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
const { data: response, isLoading: isLoadingVerdicts } = useQuery({I think with the new RPC, it makes sense to just query once between start/end pos as it should give enough info, but please correct me if i'm wrong.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
const { data: response, isLoading: isLoadingVerdicts } = useQuery({I think with the new RPC, it makes sense to just query once between start/end pos as it should give enough info, but please correct me if i'm wrong.
I don't have enough context to understand how this is integrated / how the UI looks. However:
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
const { data: response, isLoading: isLoadingVerdicts } = useQuery({Patrick MeiringI think with the new RPC, it makes sense to just query once between start/end pos as it should give enough info, but please correct me if i'm wrong.
I don't have enough context to understand how this is integrated / how the UI looks. However:
- I notice you haven't specified a sort order.
- If there are more than 1000 source verdicts, you will get the 1000 nearest source verdicts towards one of the two ends (depending on the selected sort order or the default order - this will be the most recent or the oldest results). Is this what you want?
on second thoughts i've just updated to
1) fetch up to 1000 from the end position (most recent 1000)
2) if there is more in the segment, fetches from the start position (oldest) -> only if there are >1000 segments and is recent enough.
3) combines the two arrays then splits it in half to display from each end for the UI.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |