Fix tech report pagination: Hide next/prev links based on actual data, reset to page 1 on filter changes

[Copilot]

This PR fixes the tech report pagination issue where the "Next page" link was displayed even when there were no more technologies to show, leading to 400 errors when users clicked on it.

Problem

The pagination logic had two main issues:

1. Incorrect "Next page" visibility: The template showed the "Next page" link based on the last_page parameter, which defaulted to False, meaning the link was always shown regardless of actual data availability
2. Filter changes not resetting page: When users changed filters (geo, rank, category), they could land on invalid page numbers that had no data

Solution

The fix involves three key changes:

1. Dynamic Pagination Control in Frontend

Modified src/js/techreport/utils/data.js to calculate the actual total pages based on API data and dynamically show/hide pagination links:

const totalPages = Math.ceil(category?.technologies?.length / rows);

// Hide "Next page" if on last page
if (pageNr >= totalPages) {
  nextPageLink.style.display = 'none';
} else {
  nextPageLink.style.display = 'block';
}

2. Template Updates for JavaScript Control

Updated templates/techreport/category.html to initially hide pagination links with style="display: none;" and let JavaScript control their visibility based on actual data rather than server-side logic.

3. Filter Reset to Page 1

Modified src/js/components/filters.js to automatically reset to page 1 when any filter changes:

// Reset to page 1 when filters change
url.searchParams.delete('page');
url.searchParams.append('page', '1');

Testing

• ✅ All existing tech report tests pass
• ✅ Added new tests to verify pagination links are initially hidden and controlled by JavaScript
• ✅ Manual testing confirms pagination works correctly
• ✅ Build process completed successfully

Before/After Behavior

• Before: "Next page" always visible → clicking leads to empty pages with 400 errors
• After: "Next page" only visible when there are actually more pages → smooth navigation experience

This ensures users have a better experience when browsing tech reports and eliminates the confusing 400 errors from invalid pagination requests.

Fixes #1088.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[max-ostapenko]

@copilot fix errors detected in the linting checks

[Copilot]

@copilot fix errors detected in the linting checks

Fixed the linting errors in commit 8188f5a. The issues were whitespace on blank lines in the Python test file (flake8 W293 violations). All linting checks now pass:

• ✅ Python: flake8, black, pylint
• ✅ HTML: htmlhint
• ✅ JavaScript: eslint (basic checks)

Tests continue to pass after the fix.

[max-ostapenko]

@tunetheweb wanted to get rid of the errors, so asked a friend for help.
WDYT?

[tunetheweb]

LGTM!