Fix calculation of `has_next_page` in `resolve_connection_from_cache`

[SupImDos]

Description

The strawberry_django.relay.ListConnectionWithTotalCount.resolve_connection_from_cache method currently incorrectly attempts to determine has_next_page from the QuerySet._result_cache, as opposed to the cached records within it, resulting in an AttributeError being raised.

This PR ensures that has_next_page is determined via the last record in the QuerySet._result_cache (if applicable), so that we don't get an AttributeError

Types of Changes

• [ ] Core
• [x] Bugfix
• [ ] New feature
• [ ] Enhancement/optimization
• [ ] Documentation

Issues Fixed or Closed by This PR

• Partially fixes #613

Checklist

• [x] My code follows the code style of this project.
• [ ] My change requires a change to the documentation.
• [ ] I have updated the documentation accordingly.
• [x] I have read the CONTRIBUTING document.
• [x] I have added tests to cover my changes.
• [x] I have tested the changes and verified that they work and don't break anything (as well as I can manage).

Summary by Sourcery

Fix the calculation of has_next_page in resolve_connection_from_cache to prevent an AttributeError by using the last record in the QuerySet._result_cache.

Bug Fixes:

• Fix the calculation of has_next_page in resolve_connection_from_cache to prevent an AttributeError by correctly determining it from the last record in the QuerySet._result_cache.

[sourcery-ai[bot]]

Reviewer's Guide by Sourcery

This pull request fixes a bug in the resolve_connection_from_cache method of the ListConnectionWithTotalCount class in the strawberry_django.relay module. The bug was causing an AttributeError when attempting to determine the has_next_page value. The implementation has been updated to correctly calculate has_next_page using the cached records.

File-Level Changes

Change	Details	Files
Fixed calculation of has_next_page in resolve_connection_from_cache method	Removed incorrect calculation of has_next_page using result._strawberry_row_number Added new calculation for has_next_page using the last record in result Updated has_previous_page calculation to use result[0] instead of nodes[0] Added null checks to prevent errors when result is empty	strawberry_django/relay.py

---

Tips

- Trigger a new Sourcery review by commenting `@sourcery-ai review` on the pull request. - Continue your discussion with Sourcery by replying directly to review comments. - You can change your review settings at any time by accessing your [dashboard](https://app.sourcery.ai): - Enable or disable the Sourcery-generated pull request summary or reviewer's guide; - Change the review language; - You can always [contact us](mailto:support@sourcery.ai) if you have any questions or feedback.