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
When sorting the dRep list by registration date, the API response includes dRep entries that have the doNotList flag set. These entries should be excluded from the API response to ensure that only visible dReps are displayed. This discrepancy affects pagination, as the API response might contain more items than those actually shown in the frontend.
Steps to reproduce
Navigate to the dRep Directory.
Sort the dRep list by registration date.
Observe the dRep list on the frontend.
Compare the frontend list with the dRep list returned by the API.
Actual behavior
Frontend: Displays only 9 dReps out of 10 expected due to the presence of a dRep with doNotList that is not shown.
API Response: Includes 10 dReps, including the one flagged with doNotList, which should be excluded. doNotList set dRep drep10q8zg27gca3s7gcz2l9cf2prgkwy3wypjtee36vkkw82qqfrwrk
The API response should exclude dReps with the doNotList flag to ensure consistency between the displayed list and the paginated data. This will correct the pagination issue and ensure that the number of dReps displayed matches the number of dReps returned by the API.
The text was updated successfully, but these errors were encountered:
@kneerose you are absolutely right that ideally filtering should be done on BE, however the problem is that currently db-sync does not include do_not_list column
@bosko-m Yes, in the sense that it shows correct DReps, but as @kneerose said, loading the next page might (and probably will if there are many DReps who don't want to be listed) result in a different number of added DReps. In an extreme case, if none of the fetched DReps want to be listed no DReps will show up for that page.
Area
Other
Domain
preview.gov.tools
Which wallet were you using?
No response
Context
When sorting the dRep list by registration date, the API response includes dRep entries that have the doNotList flag set. These entries should be excluded from the API response to ensure that only visible dReps are displayed. This discrepancy affects pagination, as the API response might contain more items than those actually shown in the frontend.
Steps to reproduce
Actual behavior
Frontend: Displays only 9 dReps out of 10 expected due to the presence of a dRep with doNotList that is not shown.
API Response: Includes 10 dReps, including the one flagged with doNotList, which should be excluded. doNotList set dRep
drep10q8zg27gca3s7gcz2l9cf2prgkwy3wypjtee36vkkw82qqfrwrk
Expected behavior
The API response should exclude dReps with the doNotList flag to ensure consistency between the displayed list and the paginated data. This will correct the pagination issue and ensure that the number of dReps displayed matches the number of dReps returned by the API.
The text was updated successfully, but these errors were encountered: