Add ordering by creation date to user connection queries

[Artuomka]

Summary by CodeRabbit

• New Features
  • Connection lists now sorted by creation date in reverse chronological order.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: cfb58049-3324-4209-94dd-b05b3575b17b

📥 Commits

Reviewing files that changed from the base of the PR and between 520c80f and a86a95f.

📒 Files selected for processing (1)

• backend/src/entities/connection/repository/custom-connection-repository-extension.ts

---

📝 Walkthrough

Walkthrough

Two query methods in the custom connection repository now sort results by creation date in descending order. Existing filtering logic for user ID matching and test connection flags remains unchanged.

Changes

Cohort / File(s)	Summary
Query Sorting Enhancement backend/src/entities/connection/repository/custom-connection-repository-extension.ts	Added descending sort by connection.createdAt to findAllUserConnections and findAllUserTestConnections query builders.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 Connections sorted, newest first,
A chronological burst!
Created dates in order flow,
The freshest links now steal the show! ✨

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: adding ordering by creation date to user connection queries, which matches the file summary showing new sorting by connection.createdAt in descending order.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Security Check	✅ Passed	Adding orderBy clauses to findAllUserConnections and findAllUserTestConnections methods does not introduce OWASP security vulnerabilities. TypeORM query builders use parameterized queries preventing SQL injection, existing access control filters remain unchanged, and sorting does not expose sensitive information or bypass authentication.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch backend_default_connecion_order

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull request overview

Adds explicit ordering to user connection retrieval queries so connection lists are returned in descending creation time, aligning API output with “newest first” expectations.

Changes:

• Order findAllUserConnections results by connection.createdAt DESC.
• Order findAllUserTestConnections results by connection.createdAt DESC.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Ordering solely by createdAt can be nondeterministic when multiple connections share the same timestamp (e.g., bulk inserts / same DB transaction timestamp). Consider adding a secondary deterministic sort key (via addOrderBy) to ensure stable results when createdAt ties.

[Copilot]

Same as above: ordering only by createdAt can produce unstable ordering when timestamps tie. Add a secondary deterministic ordering (e.g., addOrderBy) here as well so test-connection lists are stable.

[Copilot]

This change introduces a user-visible ordering contract (newest connections first) but existing e2e tests around GET /connections don’t appear to assert ordering. Adding/adjusting an e2e assertion would prevent regressions (especially around test vs non-test connections).