Skip to content

SANC-55: admin dashboard home page header#48

Open
tanvimahal wants to merge 4 commits intomainfrom
SANC-55-Admin-Dashboard-Home-Page-header
Open

SANC-55: admin dashboard home page header#48
tanvimahal wants to merge 4 commits intomainfrom
SANC-55-Admin-Dashboard-Home-Page-header

Conversation

@tanvimahal
Copy link
Member

@tanvimahal tanvimahal commented Jan 24, 2026

  • updated the admin navbar to match figma
  • deleted the old admin homepage
  • login redirects directly to schedules instead of the admin home

invite tab on the navbar needs to be changed from a link to the dropdown modal from SANC-64

Summary by CodeRabbit

  • Style

    • Standardized navbar padding, added bottom border, and improved link hover/active visuals for clearer navigation.
  • New Features

    • Reworked navigation: consolidated action items (View Agencies, Invite, Rider Logs, Vehicle Logs, View Schedule) and updated survey access for drivers.
  • Refactor

    • Updated admin landing to redirect to the schedule view and removed the previous admin home page.

@vercel
Copy link

vercel bot commented Jan 24, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
salvationarmy Ready Ready Preview, Comment Mar 6, 2026 0:15am

@coderabbitai
Copy link

coderabbitai bot commented Jan 24, 2026

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: a561993b-14eb-4062-9cfe-93783d2a2ef4

📥 Commits

Reviewing files that changed from the base of the PR and between 7a66ca3 and 729ef28.

📒 Files selected for processing (3)
  • src/app/_components/common/navbar.module.scss
  • src/app/_components/common/navbar.tsx
  • src/app/admin/home/page.tsx
💤 Files with no reviewable changes (1)
  • src/app/admin/home/page.tsx
🚧 Files skipped from review as they are similar to previous changes (1)
  • src/app/_components/common/navbar.module.scss

📝 Walkthrough

Walkthrough

Redesigns the navbar: new SCSS classes (.navLink, .navLinkDefault, .navLinkActive), replaces action Buttons with an internal NavLink component that uses usePathname for active state, changes admin redirect from /admin/home to /admin/schedule, and removes the admin home page file.

Changes

Cohort / File(s) Summary
Navbar Styling
src/app/_components/common/navbar.module.scss
Replaces responsive media query with uniform padding and bottom border; adds/exportss .navLink, .navLinkDefault, .navLinkActive with base link styles, hover, transitions, and font-weight states.
Navbar Component
src/app/_components/common/navbar.tsx
Adds internal NavLink (uses usePathname) to determine active state and apply SCSS classes; replaces admin/drivers action Buttons with NavLink items; adjusts header/agency rendering and removes Button imports.
Admin Routing
src/server/api/routers/organizations.ts
Changes admin redirect path from /admin/home to /admin/schedule.
Removed Page
src/app/admin/home/page.tsx
Deletes the AdminHome page and its imports (AdminDashboard, HydrateClient).

Sequence Diagram(s)

(omitted — changes are primarily component/styling replacements and a small routing redirect; no new multi-component sequential flow needing visualization)

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

Suggested reviewers

  • themaxboucher
  • burtonjong
  • promatty
  • JustinTan-1
  • wesleylui

Poem

🐰 The navbar hops with polished art,
New links that glow and play their part,
Active paths the rabbit spies,
Padding snug where the logo lies,
Off to schedules now we dart! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title references updating the admin navbar header, which aligns with the navbar styling and structure changes, but omits the significant changes of deleting the admin home page and updating redirect logic.

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

✨ Finishing Touches
  • 📝 Generate docstrings (stacked PR)
  • 📝 Generate docstrings (commit on current branch)
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch SANC-55-Admin-Dashboard-Home-Page-header

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

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

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In `@src/app/_components/common/navbar.tsx`:
- Around line 44-48: Navbar contains NavLink entries that point to non-existent
admin routes (/admin/agencies, /admin/invite, /admin/vehicle-logs) which cause
404s; either implement the missing pages or update the NavLink instances in
navbar.tsx: remove or replace the NavLink href="/admin/agencies" and
href="/admin/invite" with correct existing routes (or add new pages matching
those hrefs), and change href="/admin/vehicle-logs" to the existing route (e.g.,
href="/admin/driver-logs" or another correct path); update the NavLink elements’
text accordingly so links and targets match actual route components.
🧹 Nitpick comments (3)
src/app/_components/common/navbar.module.scss (1)

11-14: Duplicate style declaration for .navLinkDefault.

The font-weight: 400 property is declared twice for .navLinkDefault (lines 12 and 30). Additionally, the transition: color 0.2s ease on line 13 is overwritten by transition: background-color 0.2s ease on line 20 (since CSS transition shorthand replaces, not merges). Consider consolidating:

♻️ Suggested consolidation
 .navLinkDefault,
 .navLinkActive {
     font-size: 0.75rem;
     cursor: pointer;
-    transition: background-color 0.2s ease;
+    transition: background-color 0.2s ease, color 0.2s ease;
     padding: 0.5rem 0.75rem;
     border-radius: 4px;
 }
 
 .navLinkDefault:hover {
     background-color: `#f3f4f6`;
 }
 
-.navLinkDefault {
-    font-weight: 400;
-}
-
 .navLinkActive {
     font-weight: 600;
 }

Also applies to: 29-31

src/app/_components/common/navbar.tsx (2)

36-36: SCSS .navbar class is imported but not used; inline styles duplicate it.

The SCSS module defines .navbar with padding: 1rem 2rem; border-bottom: 1px solid #e5e7eb; but line 36 uses inline styles and the "border-bottom" className (likely a global/Tailwind class). Consider using the imported SCSS class for consistency:

♻️ Suggested change
-    <Group justify="space-between" className="border-bottom" style={{ padding: "1rem 2rem" }}>
+    <Group justify="space-between" className={styles.navbar}>

23-32: Consider startsWith for nested route highlighting.

The current exact match (pathname === href) won't mark a link as active when navigating to child routes (e.g., /admin/schedule/123 won't highlight "View Schedule"). If nested routes exist or are planned, consider:

const isActive = pathname === href || pathname.startsWith(`${href}/`);

This is optional depending on your route structure.

Comment on lines +44 to +48
<NavLink href="/admin/agencies">View Agencies</NavLink>
<NavLink href="/admin/invite">Invite</NavLink>
<NavLink href="/admin/rider-logs">Rider Logs</NavLink>
<NavLink href="/admin/vehicle-logs">Vehicle Log</NavLink>
<NavLink href="/admin/schedule">View Schedule</NavLink>
Copy link

@coderabbitai coderabbitai bot Jan 24, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Check for admin route pages/directories

echo "=== Checking admin app directory structure ==="
if [ -d "src/app/admin" ]; then
  echo "Admin directory found. Contents:"
  ls -la src/app/admin 2>/dev/null || echo "Cannot list admin directory"
  echo ""
  
  # Check for specific route directories
  routes=("agencies" "invite" "rider-logs" "vehicle-logs" "schedule")
  echo "=== Checking for expected route directories/pages ==="
  for route in "${routes[@]}"; do
    if [ -d "src/app/admin/$route" ]; then
      echo "$route: Directory found"
      # Check if it has a page.tsx or page.ts
      if [ -f "src/app/admin/$route/page.tsx" ] || [ -f "src/app/admin/$route/page.ts" ]; then
        echo "  └─ Has page component"
      fi
    elif [ -f "src/app/admin/$route.tsx" ] || [ -f "src/app/admin/$route.ts" ]; then
      echo "$route: File found"
    else
      echo "$route: NOT FOUND"
    fi
  done
else
  echo "Admin directory not found at src/app/admin"
fi

Repository: Code-the-Change-YYC/salvationarmy

Length of output: 809


Remove or create the missing admin routes.

The navbar links to /admin/agencies, /admin/invite, and /admin/vehicle-logs, but these pages do not exist in the codebase. Clicking these links will result in 404 errors. Either create these missing route pages or remove the broken links and replace with the routes that do exist (driver-logs, rider-logs, schedule).

🤖 Prompt for AI Agents
In `@src/app/_components/common/navbar.tsx` around lines 44 - 48, Navbar contains
NavLink entries that point to non-existent admin routes (/admin/agencies,
/admin/invite, /admin/vehicle-logs) which cause 404s; either implement the
missing pages or update the NavLink instances in navbar.tsx: remove or replace
the NavLink href="/admin/agencies" and href="/admin/invite" with correct
existing routes (or add new pages matching those hrefs), and change
href="/admin/vehicle-logs" to the existing route (e.g.,
href="/admin/driver-logs" or another correct path); update the NavLink elements’
text accordingly so links and targets match actual route components.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

instead of admin/vehicle-logs the endpoint is admin/driver-logs

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Verify the driver-logs route exists and check vehicle-logs
echo "=== Checking for driver-logs route ==="
if [ -d "src/app/admin/driver-logs" ]; then
  echo "✓ driver-logs directory exists"
  ls -la src/app/admin/driver-logs
elif [ -f "src/app/admin/driver-logs.tsx" ] || [ -f "src/app/admin/driver-logs.ts" ]; then
  echo "✓ driver-logs file exists"
fi

echo ""
echo "=== Checking for vehicle-logs route ==="
if [ -d "src/app/admin/vehicle-logs" ]; then
  echo "✓ vehicle-logs directory exists"
  ls -la src/app/admin/vehicle-logs
elif [ -f "src/app/admin/vehicle-logs.tsx" ] || [ -f "src/app/admin/vehicle-logs.ts" ]; then
  echo "✓ vehicle-logs file exists"
else
  echo "✗ vehicle-logs does NOT exist"
fi

echo ""
echo "=== Current navbar.tsx NavLink for vehicle/driver logs ==="
rg -n "vehicle-logs|driver-logs" src/app/_components/common/navbar.tsx

Length of output: 437


@promatty, thank you for the clarification! You're right—the navbar should link to /admin/driver-logs, not /admin/vehicle-logs.

Line 47 currently has:

<NavLink href="/admin/vehicle-logs">Vehicle Log</NavLink>

This should be updated to:

<NavLink href="/admin/driver-logs">Vehicle Log</NavLink>

The /admin/driver-logs route exists in the codebase, so this will fix the 404 for that link. However, /admin/agencies and /admin/invite still need to be addressed (either created or removed from the navbar).


🧬 Code Graph Analysis Results

[src/app/_components/common/navbar.tsx] (lines 1- end)

"use client";

import { Group, Text } from "@mantine/core";
import Link from "next/link";
import { usePathname } from "next/navigation";
import Bell from "@/assets/icons/bell";
import Home from "@/assets/icons/home";
import styles from "./navbar.module.scss";
import Profile from "./profile/profile";

type NavbarView = "admin" | "agency" | "driver";

interface NavbarProps {
  view: NavbarView;
  agencyName?: string; //only used in Agency View
}

interface NavLinkProps {
  href: string;
  children: React.ReactNode;
}

function NavLink({ href, children }: NavLinkProps) {
  const pathname = usePathname();
  const isActive = pathname === href;

  return (
    <Link href={href} className={styles.navLink}>
      <span className={isActive ? styles.navLinkActive : styles.navLinkDefault}>{children}</span>
    </Link>
  );
}

export default function Navbar({ view, agencyName }: NavbarProps) {
  return (
    <Group justify="space-between" className="border-bottom" style={{ padding: "1rem 2rem" }}>
      <Group>
        <Home />
        <Text>{view === "agency" ? `${agencyName ?? "[Agency name]"} Home` : ""}</Text>
      </Group>

      {view === "admin" && (
        <Group gap={30}>
          <NavLink href="/admin/agencies">View Agencies</NavLink>
          <NavLink href="/admin/invite">Invite</NavLink>
          <NavLink href="/admin/rider-logs">Rider Logs</NavLink>
          <NavLink href="/admin/vehicle-logs">Vehicle Log</NavLink>
          <NavLink href="/admin/schedule">View Schedule</NavLink>
          <Profile />
        </Group>
      )}

      {view === "agency" && (
        <Group gap={30}>
          <Bell />
          <Profile />
        </Group>
      )}

      {view === "driver" && (
        <Group>
          <Profile />
        </Group>
      )}
    </Group>
  );
}

✏️ Learnings added
Learnt from: promatty
Repo: Code-the-Change-YYC/salvationarmy PR: 48
File: src/app/_components/common/navbar.tsx:44-48
Timestamp: 2026-01-24T06:06:38.145Z
Learning: In the Salvation Army project, the correct admin route for vehicle/driver logs is `/admin/driver-logs`, not `/admin/vehicle-logs`.

Note: Learnings are effective only in the context of similar code segments. To apply general coding guidelines, please configure review instructions. You can manage existing learnings in the app.

Copy link
Contributor

@promatty promatty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also, in app/page.tsx can we redirect to the schedule page instead of admin/home

</Link>
<Group gap={30}>
<NavLink href="/admin/agencies">View Agencies</NavLink>
<NavLink href="/admin/invite">Invite</NavLink>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we make this open the invite modal we currently have, instead of waiting for sanc-64

Comment on lines +44 to +48
<NavLink href="/admin/agencies">View Agencies</NavLink>
<NavLink href="/admin/invite">Invite</NavLink>
<NavLink href="/admin/rider-logs">Rider Logs</NavLink>
<NavLink href="/admin/vehicle-logs">Vehicle Log</NavLink>
<NavLink href="/admin/schedule">View Schedule</NavLink>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

instead of admin/vehicle-logs the endpoint is admin/driver-logs

@burtonjong
Copy link
Contributor

@tanvimahal merge conflicts

@promatty
Copy link
Contributor

promatty commented Feb 9, 2026

@tanvimahal bump

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
src/app/_components/common/navbar.tsx (1)

39-61: 🛠️ Refactor suggestion | 🟠 Major

Remove dead code: navbarText() and homeLink() are unused.

Neither function is called in the returned JSX. Additionally, homeLink() still references the stale /admin/home path. These should be cleaned up.

Proposed fix
 export default function Navbar({ view, agencyName }: NavbarProps) {
-  const pathname = usePathname();
-
-  const section = pathname.split("/")[2] ?? "home";
-
-  const navbarText = () => {
-    switch (view) {
-      case "admin":
-        return `Admin ${section}`;
-      case "agency":
-        return `${agencyName ?? "[Agency name]"} ${section}`;
-      case "driver":
-        return `Driver ${section}`;
-      default:
-        return "";
-    }
-  };
-
-  const homeLink = () => {
-    switch (view) {
-      case "admin":
-        return `/admin/home`;
-      case "agency":
-        return `/agency/home`;
-      case "driver":
-        return `/driver/home`;
-    }
-  };
-
   return (
🧹 Nitpick comments (1)
src/app/_components/common/navbar.tsx (1)

18-32: NavLink component looks good overall.

Clean implementation with active state detection. One minor optimization: each NavLink instance independently calls usePathname(). Since the parent Navbar already calls it (line 35), consider passing pathname as a prop to avoid redundant hook calls across all NavLink instances.

@tanvimahal tanvimahal requested a review from promatty February 9, 2026 01:42
<Group gap={30}>
<NavLink href="/admin/agencies">View Agencies</NavLink>
<NavLink href="/admin/invite">Invite</NavLink>
<NavLink href="/admin/rider-logs">Rider Logs</NavLink>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the invite tab should bring up the invite modal. this only exists on the http://localhost:3000/admin/home button right now. i also thought we were going to remove admin/home?

@promatty
Copy link
Contributor

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

src/app/_components/common/navbar.tsx (1)> 39-61: 🛠️ Refactor suggestion | 🟠 Major

Remove dead code: navbarText() and homeLink() are unused.
Neither function is called in the returned JSX. Additionally, homeLink() still references the stale /admin/home path. These should be cleaned up.

Proposed fix

 export default function Navbar({ view, agencyName }: NavbarProps) {
-  const pathname = usePathname();
-
-  const section = pathname.split("/")[2] ?? "home";
-
-  const navbarText = () => {
-    switch (view) {
-      case "admin":
-        return `Admin ${section}`;
-      case "agency":
-        return `${agencyName ?? "[Agency name]"} ${section}`;
-      case "driver":
-        return `Driver ${section}`;
-      default:
-        return "";
-    }
-  };
-
-  const homeLink = () => {
-    switch (view) {
-      case "admin":
-        return `/admin/home`;
-      case "agency":
-        return `/agency/home`;
-      case "driver":
-        return `/driver/home`;
-    }
-  };
-
   return (

🧹 Nitpick comments (1)

remove unused functions

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
src/app/_components/common/navbar.tsx (1)

35-61: 🛠️ Refactor suggestion | 🟠 Major

Remove unused navbarText(), homeLink() functions and section variable.

These functions are defined but never called anywhere in the component. Additionally, homeLink() references the stale /admin/home path which is being removed per the PR description. The section variable (line 37) is only used by navbarText(), making it dead code as well.

🧹 Proposed removal of dead code
 export default function Navbar({ view, agencyName }: NavbarProps) {
-  const pathname = usePathname();
-
-  const section = pathname.split("/")[2] ?? "home";
-
-  const navbarText = () => {
-    switch (view) {
-      case "admin":
-        return `Admin ${section}`;
-      case "agency":
-        return `${agencyName ?? "[Agency name]"} ${section}`;
-      case "driver":
-        return `Driver ${section}`;
-      default:
-        return "";
-    }
-  };
-
-  const homeLink = () => {
-    switch (view) {
-      case "admin":
-        return `/admin/home`;
-      case "agency":
-        return `/agency/home`;
-      case "driver":
-        return `/driver/home`;
-    }
-  };
-
   return (
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@src/app/_components/common/navbar.tsx` around lines 35 - 61, Remove the dead
code: delete the section constant and the navbarText() and homeLink() functions
from the component (they're unused and homeLink() still returns the stale
`/admin/home` path). Search for references to navbarText, homeLink, and section
to confirm none remain; if other code expects a home path, replace usages with
the new routing logic elsewhere rather than restoring homeLink. Keep view and
agencyName as-is if they are used elsewhere.
🧹 Nitpick comments (1)
src/app/_components/common/navbar.module.scss (1)

11-14: Duplicate font-weight: 400 declaration for .navLinkDefault.

font-weight: 400 is declared twice for .navLinkDefault (lines 12 and 30). Additionally, the transition property at line 13 (color 0.2s ease) is overwritten by line 20 (background-color 0.2s ease), so the color transition won't apply.

Consider consolidating into a single block or combining transitions:

♻️ Proposed consolidation
 .navLinkDefault {
     font-weight: 400;
-    transition: color 0.2s ease;
+    transition: color 0.2s ease, background-color 0.2s ease;
 }

 .navLinkDefault,
 .navLinkActive {
     font-size: 0.75rem;
     cursor: pointer;
-    transition: background-color 0.2s ease;
     padding: 0.5rem 0.75rem;
     border-radius: 4px;
 }

 .navLinkDefault:hover {
     background-color: var(--color-light-grey);
 }

-.navLinkDefault {
-    font-weight: 400;
-}
-
 .navLinkActive {
     font-weight: 600;
+    transition: background-color 0.2s ease;
 }

Also applies to: 29-31

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@src/app/_components/common/navbar.module.scss` around lines 11 - 14, The
.navLinkDefault rules contain duplicated font-weight and conflicting transition
declarations; remove the duplicate font-weight and consolidate the transition
declarations for .navLinkDefault so both color and background-color animate
(e.g., use a single .navLinkDefault rule that keeps font-weight: 400 and a
combined transition like "transition: color 0.2s ease, background-color 0.2s
ease"). Update any other duplicate blocks (the one around lines 29-31) to use
the same consolidated rule so there’s only one .navLinkDefault definition.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Outside diff comments:
In `@src/app/_components/common/navbar.tsx`:
- Around line 35-61: Remove the dead code: delete the section constant and the
navbarText() and homeLink() functions from the component (they're unused and
homeLink() still returns the stale `/admin/home` path). Search for references to
navbarText, homeLink, and section to confirm none remain; if other code expects
a home path, replace usages with the new routing logic elsewhere rather than
restoring homeLink. Keep view and agencyName as-is if they are used elsewhere.

---

Nitpick comments:
In `@src/app/_components/common/navbar.module.scss`:
- Around line 11-14: The .navLinkDefault rules contain duplicated font-weight
and conflicting transition declarations; remove the duplicate font-weight and
consolidate the transition declarations for .navLinkDefault so both color and
background-color animate (e.g., use a single .navLinkDefault rule that keeps
font-weight: 400 and a combined transition like "transition: color 0.2s ease,
background-color 0.2s ease"). Update any other duplicate blocks (the one around
lines 29-31) to use the same consolidated rule so there’s only one
.navLinkDefault definition.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 698cbd51-ad22-4f1a-be11-20c9dd4052da

📥 Commits

Reviewing files that changed from the base of the PR and between 0f0c6bc and 7a66ca3.

📒 Files selected for processing (3)
  • src/app/_components/common/navbar.module.scss
  • src/app/_components/common/navbar.tsx
  • src/server/api/routers/organizations.ts
🚧 Files skipped from review as they are similar to previous changes (1)
  • src/server/api/routers/organizations.ts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants