You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, meta just has the limit and offset that was requested, but I think we should also add the limit and offset for next, last, etc (i.e. the numeric values for each the links). This makes using clients a lot easier because you don't have to parse the links for the values. I'm picturing something like the following in addition to the links.
So i actually wanted to create same issue when i started using the pagination in UI. But because of how the PF4 pagination works this is not really necessary and limit + offset is enough. I can definitely imagine that these might be useful but i don't have a real use case for that right now (from UI perspective).
The only scenario this can be issue right now is if the first offset is not 0. I don't expect that ever happen though.
It should be probably added down the line but it is not urgent i think.
Right now, meta just has the limit and offset that was requested, but I think we should also add the limit and offset for next, last, etc (i.e. the numeric values for each the links). This makes using clients a lot easier because you don't have to parse the links for the values. I'm picturing something like the following in addition to the links.
The text was updated successfully, but these errors were encountered: