79 feat projects order and filter buttons

[Rafetikus]

This pull request significantly enhances the filtering, sorting, and user experience of the ProjectsListPage component. The changes introduce support for multiple URL-based filters (such as access, lead, member, date, and favorites), add sorting options, and improve the empty state messaging to better reflect the user's filter selections.

Filtering and Sorting Improvements:

• Added parsing of URL search parameters to support filtering projects by access type (private/public), project lead, members, creation date, favorites, and "my projects only". These filters are now applied in sequence to the project list. [1] [2]
• Implemented robust sorting logic for projects, allowing sorting by name, creation date, member count, and manual order, with both ascending and descending directions.

User Experience Enhancements:

• Improved the empty state message: now displays "No projects match the selected filters." if any filters are active and no projects are found, otherwise shows "No projects yet."
• Simplified the logic for closing the "create project" modal by directly manipulating the search parameters, improving code clarity.

Authentication Context Usage:

• Integrated the useAuth context to enable filtering projects by the currently authenticated user (for "my projects only" filter). [1] [2] [3]
  closes Feat: projects order and filter buttons #79

[Copilot]

Pull request overview

Adds sorting and richer filtering controls for the workspace Projects list, wiring UI query params in the header to client-side filtering/sorting on the list page (Issue #79).

Changes:

• Add query-param driven filtering (access, lead, members, created-date, “my projects”, favorites) and sorting logic to the projects list.
• Replace placeholder header buttons with functional Sort and Filters dropdowns (including workspace member lookups for lead/member filters).
• Improve empty-state messaging when filters are active.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File	Description
ui/src/pages/ProjectsListPage.tsx	Parses filter/sort params from the URL and applies filtering + sorting to the projects collection.
ui/src/components/layout/PageHeader.tsx	Implements “Sort projects” and “Filter projects” dropdowns that write filter/sort state into URL search params.

---

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

[nazarli-shabnam]

consider copilot comments, and re-request review from me

[nazarli-shabnam]

improve search query.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.

---

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

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

---

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

[Javenn0]

Well done!

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated 5 comments.

---

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

[Rafetikus]

@nazarli-shabnam quick review

[Rafetikus]

ctrl+enter AND enter should work in project settings->add member

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

---

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

[Copilot]

memberFilters depends on membersByProject, but while members are still loading membersByProject[p.id] is [], which makes this filter exclude every project (temporary empty list / misleading empty-state) whenever a member filter is active. Consider tracking a “membersByProjectLoaded” boolean (e.g., keys count === allProjects.length) and either (a) show a loading indicator while filters require member data, or (b) treat missing member data as “unknown” and keep projects until the member list has loaded.

[Copilot]

myProjectsOnly has the same issue as the member filter: until membersByProject finishes loading, memberIds is [] so this condition filters out projects the user may belong to, causing a brief “no projects” state. Consider gating this filter on member-data readiness (or showing a loading state) to avoid flicker and incorrect empty messaging.

Suggested change

	const memberIds = membersByProject[p.id] ?? [];
	return memberFilters.some(
	(memberId) => memberIds.includes(memberId) || p.project_lead_id === memberId,
	);
	})
	.filter((p) => {
	if (!myProjectsOnly || !authUser) return true;
	const memberIds = membersByProject[p.id] ?? [];
	const hasMembersLoaded = Object.prototype.hasOwnProperty.call(membersByProject, p.id);
	if (!hasMembersLoaded) return true;
	const memberIds = membersByProject[p.id];
	return memberFilters.some(
	(memberId) => memberIds.includes(memberId) || p.project_lead_id === memberId,
	);
	})
	.filter((p) => {
	if (!myProjectsOnly || !authUser) return true;
	const hasMembersLoaded = Object.prototype.hasOwnProperty.call(membersByProject, p.id);
	if (!hasMembersLoaded) return true;
	const memberIds = membersByProject[p.id];

[Copilot]

For createdDateFilter === 'custom', the filter is effectively disabled unless both createdAfter and createdBefore parse to finite timestamps (if (!Number.isFinite(afterMs) || !Number.isFinite(beforeMs)) return true). This makes the UI state inconsistent if one bound is missing/invalid (e.g. URL edited manually): the filter appears active but doesn’t filter anything. Consider supporting open-ended ranges (only after / only before) and treating invalid bounds as non-matching (or clearing the custom filter).