Closed dinmukhamedm closed 2 weeks ago
@dinmukhamedm Hey! Could we work on this together? I’ll ask for help if I run into any issues.
Sure @sarthakvijayvargiya let's work together. I gave it another thought, and I think it makes sense to control/parse the page size and page number to/from the URL params right inside the DataTablePagination
component. Let me know if you have further questions!
Thanks for the guidance! I don't have any questions right now, but I’ll reach out if anything comes up.
Hi @dinmukhamedm to reproduce this issue, should I set up a dummy project and integrate Laminar into it, or is there another way to replicate the bug?
@sarthakvijayvargiya First off when you spin up laminar locally, you will have to create a Laminar project any way. Then you have two options:
observe
your functions.cd frontend && npx drizzle-kit studio
I will add some SQL fake data to this comment a little bit later today, but let me know if you managed to go with option 1
I tried above steps - I have started laminar locally , created project.
observe
function ,but kept getting this error
Fixed via #208
This is true for any table with [manual] pagination, spans and traces are a good candidate
Reproduction step
Expected behavior
I can see my traces for the last hour
Actual behavior
I see an empty page, because I am in page 3/1
TODO: Reset pageNumber to 0 when filters change. We can be smart here, e.g. do this only if filters change or if the time range decreases. If we merely increase the time range, it probably makes sense to stay on the same page