Pager on /athletes page

The /athletes page now has a pager. This should fix the 429 errors for people with lots of athletes.

The paging is applied after tag searching and there are 10 athletes per page. All the tabs now show data only from the currently selected page.

I am going to be doing some more work in this area and will likely be able to make the page size bigger soon.

1 Like

I don’t like it, missing comments and overview.
can I turn it off?

Do you have 10 athletes on each page? I first deployed a buggy version with only 2 per page (I was testing).

Yes but now I don’t have a full overview. When I open up. I first check new comments, now I can not see who sent one in a glance.

  • I have one single athlete on my last page. And it is always the same ones on the last page, so that makes me think I look at them less than first pagers.

Maybe it would help if the order of athletes changes to the latest uploaded activity to the top. Or latest comment to the top. And not alphabetically.

Or just make an option to put it off.

What is the actual reason for it? loading time on front page?

1 Like

The server has rate limiting to defend against bugs in the client application etc… If a user makes too many calls in a short timeframe they fail with 429 errors. That happens when the app tries to load data for many athletes at once. It has been happening quite a lot.

I am working on a solution that will allow a bigger page size but there will have to be pages. Some people have hundreds of athletes.

I will also see if I can do something with the sort order.

Yes ok clear! I do use the filter option to avoid big list of athletes.
That works great. and the page size change can help.
Sort order would be nice

thanks for the reply!

I don’t like it either. Can we have the option to add more than 10 athletes?

Good morning,

As already mentioned here, I prefer the previous version, where I can see all the ones I filtered and I can also have a quick view of new comments!

I hope you can maintain the previous standard and without errors, or both options.

Would a more simplified and streamlined Overview tab be a possible solution?

On the platform I used previously, we just had a list of names—no photo, no summary data. Between having no data and having athletes split across multiple pages, I personally prefer the more simplified option, if it’s a possibility.

The page size is now 30 and there is client side rate limiting. I am going to do some more work on this later on the weekend.

I will look into that.

2 Likes

Hi David,
In the ‘Activities’ tab of the Athletes page, each activity is ordered by the date it was created. However, athletes who don’t appear on the first page of the ‘Overview’ tab (above the limit set in this update) are also not properly ordered in the ‘Activities’ tab.

Would it be possible for the ‘Activities’ tab to sort all athletes solely based on the ‘date created’ field, regardless of their visibility in the overview? To avoid data volume issues, maybe even by reducing the number of rows/activities displayed.

Unfortunately it is not easy to do that. To make the “Activities” tab sort without regarding the pager would require fetching recent activities for all athletes, which is what I need to avoid.

1 Like