feat(activists): activist details page#345
Merged
Conversation
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughAdds an Activist detail page (SSR + client hydration), a new backend GET /api/activists/{id} endpoint with organizer-scoped access, SSR HTTP-error routing helper rename/behavior change, formatting/linking utilities for activist fields, and related UI/import/path updates and docs. Changes
Sequence Diagram(s)sequenceDiagram
actor User
participant Browser as Browser / Next.js
participant SSR as SSR (Next)
participant API as Go API Server
participant DB as Database
User->>Browser: Navigate to /activists/{id}
Browser->>SSR: Request SSR page
SSR->>SSR: parse id, build ApiClient with cookies
SSR->>API: GET /api/activists/{id}
API->>API: ActivistGetHandler (auth + params)
API->>DB: GetActivistJSONForUser(db, authedUser, options)
alt validation error
DB-->>API: ErrValidation
API-->>SSR: 400 Bad Request
else not found / chapter mismatch
DB-->>API: ErrNotFound
API-->>SSR: 404 Not Found
else success
DB-->>API: ActivistJSON
API-->>SSR: 200 + {activist}
SSR->>SSR: dehydrate QueryClient
SSR-->>Browser: HTML + hydrated state
Browser->>Browser: Hydrate and render ActivistDetail
Browser->>Browser: formatValue + LinkedValue render fields
end
Estimated code review effort🎯 4 (Complex) | ⏱️ ~45 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
📝 Coding Plan
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 7
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
frontend-v2/src/app/(authed)/activists/activists-table.tsx (1)
183-210: 🧹 Nitpick | 🔵 TrivialConsider avoiding
href="#"fallback.When
activist.idis falsy, usinghref="#"causes the page to scroll to the top on click, which is a poor UX. Since activists without IDs shouldn't occur in practice (they come from the database), consider either:
- Conditionally rendering a non-interactive
<div>instead of a link- Using
href={undefined}and letting the link be non-functional♻️ Optional: Conditional wrapper to avoid href="#"
- {activists.map((activist) => ( - <IntentPrefetchLink + {activists.map((activist) => { + const Wrapper = activist.id + ? ({ children, className }: { children: React.ReactNode; className: string }) => ( + <IntentPrefetchLink + href={`/activists/${activist.id}`} + className={className} + > + {children} + </IntentPrefetchLink> + ) + : ({ children, className }: { children: React.ReactNode; className: string }) => ( + <div className={className}>{children}</div> + ) + + return ( + <Wrapper key={activist.id} - href={activist.id ? `/activists/${activist.id}` : '#'} className={`block rounded-lg border bg-card p-4 transition-opacity hover:border-primary/50 ${ isStale ? 'opacity-60' : '' }`} >🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@frontend-v2/src/app/`(authed)/activists/activists-table.tsx around lines 183 - 210, The current IntentPrefetchLink uses href="#" when activist.id is falsy which causes scroll-to-top; update the render to avoid a "#": conditionally render an interactive IntentPrefetchLink only when activist.id exists (use href={`/activists/${activist.id}`}) and render a non-interactive wrapper (e.g., a <div> with the same className and children) when activist.id is missing, keeping the inner mapping over visibleColumns, COLUMN_DEFINITIONS, formatValue and ActivistJSON references unchanged; alternatively set href={undefined} on IntentPrefetchLink when activist.id is falsy so the link is non-functional instead of pointing to "#".
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@AGENTS.md`:
- Line 13: Update the documentation text that references the old helper name
`redirectIfForbidden` to the new `redirectForHttpError` helper (and adjust any
explanatory examples or notes to call the new symbol), ensuring the guidance
still recommends using `fetchQuery` (not `prefetchQuery`) so 403s surface during
SSR; search for occurrences of `redirectIfForbidden` in the AGENTS.md content
and replace them with `redirectForHttpError`, and update any example code
snippets and surrounding wording to match the new helper signature and behavior.
In `@frontend-v2/src/app/`(authed)/activists/[id]/activist-detail.tsx:
- Around line 26-29: The component ActivistDetail currently returns null when
the hook useActivist(activistId) yields undefined, which hides UI during
client-side fetches; replace the early `if (!activist) return null` with a
loading state (spinner/skeleton) and/or use the hook's loading status if
available (e.g., isLoading or similar) to render a placeholder until activist
data is present; update the rendering logic in ActivistDetail to show the
loading indicator for client-side navigation and then render the full activist
UI once `activist` is defined.
In `@frontend-v2/src/app/`(authed)/activists/linked-value.tsx:
- Around line 11-12: The URL branch (case 'url' in linked-value.tsx) is too
strict — it only returns values that start with 'https' so http,
protocol-relative, or bare domains become non-clickable; replace the startsWith
check with a normalization/validation step (e.g., add a normalizeUrl(value)
helper called from the URL branch) that: 1) trims input, 2) converts
protocol-relative URLs ("//...") to "https://...", 3) prepends "https://" for
bare domains or known social domains (facebook.com, twitter.com, instagram.com,
etc.), 4) accepts "http://" by normalizing to "https://" or at least allowing it
as a clickable href, and 5) validates using the URL constructor (or a regex) and
returns null for invalid results; update the URL branch in linked-value.tsx to
call this helper and use the normalized href for clickable links.
In `@frontend-v2/src/lib/api.ts`:
- Around line 393-401: The detail fetch currently returns the parsed activist
directly which can leave numeric fields undefined; update getActivist to
normalize omitted zero-valued numeric fields after parsing by calling a helper
like fillSingleActivistBlankNumericFieldsWithZero(activist) (or implement that
logic in-place) so any BLANK_TO_ZERO_FIELDS (e.g., total_events,
months_since_last_action, total_points, total_interactions) that are undefined
are set to 0 before returning; locate getActivist and
ActivistGetResp.parse(resp).activist and ensure the normalized object is
returned instead of the raw parsed activist.
In `@server/src/model/activist_test.go`:
- Around line 470-508: Add a test that verifies GetActivistJSONForUser rejects a
non-admin from a different valid chapter: use GetOrCreateActivist to create an
activist in SFBayChapterIdDevTest (as in sfBayActivist), create a second real
chapter fixture ID (e.g., otherChapterID or OtherChapterIdDevTest), then call
GetActivistJSONForUser passing an ADBUser with Roles excluding admin and
ChapterID set to that other chapter and GetActivistOptions{ID:
sfBayActivist.ID}; assert it returns the same scoping error as GetActivistJSON
(ErrNotFound) to ensure user.ChapterID is being forwarded and cross-chapter
access is denied.
In `@server/src/model/activist.go`:
- Around line 889-890: You added the "a.hidden = false" predicate into the
shared activist query, which breaks callers that expect hidden rows (notably
UserUpdateActivist that calls GetActivistsExtra/GetActivistOptions and
immediately indexes orig[0]); either remove/move that predicate into the
caller-facing JSON helpers (GetActivistJSON / GetActivistJSONForUser) so the
shared lookup still returns hidden rows for internal callers, or add a defensive
check in UserUpdateActivist to reject zero-length results before indexing and
return a proper error; update the code paths referencing GetActivistsExtra,
GetActivistOptions, UserUpdateActivist, and
GetActivistJSON/GetActivistJSONForUser accordingly so hidden filtering is
applied only at the API layer or handled with a safe nil/empty check.
- Around line 30-31: Legacy callers of GetActivistJSON are invoking the old
sendErrorMessage(w, err) which doesn't map ErrNotFound or ErrValidation to
proper HTTP status codes; update those callers (the ones that call
sendErrorMessage from main.go) to either 1) detect error types using
errors.Is(err, model.ErrNotFound) and errors.Is(err, model.ErrValidation) and
pass the appropriate status via the newer transport sendErrorMessage(w, status,
err), or 2) replace the old sendErrorMessage(w, err) calls with direct calls to
the new sendErrorMessage(w, http.StatusNotFound/BadRequest/InternalServerError,
err) so that ErrNotFound and ErrValidation are returned with correct HTTP status
codes; ensure you reference GetActivistJSON and the ErrNotFound/ErrValidation
symbols when making these changes.
---
Outside diff comments:
In `@frontend-v2/src/app/`(authed)/activists/activists-table.tsx:
- Around line 183-210: The current IntentPrefetchLink uses href="#" when
activist.id is falsy which causes scroll-to-top; update the render to avoid a
"#": conditionally render an interactive IntentPrefetchLink only when
activist.id exists (use href={`/activists/${activist.id}`}) and render a
non-interactive wrapper (e.g., a <div> with the same className and children)
when activist.id is missing, keeping the inner mapping over visibleColumns,
COLUMN_DEFINITIONS, formatValue and ActivistJSON references unchanged;
alternatively set href={undefined} on IntentPrefetchLink when activist.id is
falsy so the link is non-functional instead of pointing to "#".
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: 83e5f64b-5c18-4ae8-93c3-0e5d02be60f9
📒 Files selected for processing (30)
AGENTS.mdfrontend-v2/src/app/(authed)/activists/[id]/activist-detail.tsxfrontend-v2/src/app/(authed)/activists/[id]/loading.tsxfrontend-v2/src/app/(authed)/activists/[id]/page.tsxfrontend-v2/src/app/(authed)/activists/activists-table.tsxfrontend-v2/src/app/(authed)/activists/column-definitions.tsfrontend-v2/src/app/(authed)/activists/filter-api-transform.tsfrontend-v2/src/app/(authed)/activists/filter-url-codecs.tsfrontend-v2/src/app/(authed)/activists/filters/date-range-filter.tsxfrontend-v2/src/app/(authed)/activists/filters/int-range-filter.tsxfrontend-v2/src/app/(authed)/activists/format-value.tsfrontend-v2/src/app/(authed)/activists/linked-value.tsxfrontend-v2/src/app/(authed)/activists/page.tsxfrontend-v2/src/app/(authed)/coachings/[id]/page.tsxfrontend-v2/src/app/(authed)/events/[id]/page.tsxfrontend-v2/src/app/(authed)/interest/generator/page.tsxfrontend-v2/src/app/(authed)/intl/organizers/page.tsxfrontend-v2/src/app/(authed)/users/[id]/page.tsxfrontend-v2/src/app/(authed)/users/new/page.tsxfrontend-v2/src/app/(authed)/users/page.tsxfrontend-v2/src/app/not-found.tsxfrontend-v2/src/app/site-background-controller.tsxfrontend-v2/src/lib/api.tsfrontend-v2/src/lib/number-utils.tsfrontend-v2/src/lib/server-auth.tsserver/src/main.goserver/src/model/activist.goserver/src/model/activist_test.goserver/src/model/event.goserver/src/transport/activists.go
alexsapps
force-pushed
the
alex/view-activist
branch
from
79c6953 to
f0325e2
Compare
There was a problem hiding this comment.
Actionable comments posted: 5
♻️ Duplicate comments (1)
server/src/model/activist.go (1)
581-596:⚠️ Potential issue | 🟠 MajorFilter hidden activists in the API-facing lookup.
GetActivistJSONForUsernow backs the public detail endpoint, but it delegates to an ID lookup that still skipsa.hidden = false. A direct/api/activists/{id}request can therefore return a hidden/merged activist that never appears in list views. Keep that filter in this helper (or another API-only helper) instead of the shared ID query so internal callers likeUserUpdateActivistcan still load hidden rows safely.💡 Suggested fix
func GetActivistJSONForUser(db *sqlx.DB, authedUser ADBUser, options GetActivistOptions) (ActivistJSON, error) { if !UserHasOrganizerAccess(authedUser) { return ActivistJSON{}, ValidationErrorf("lacking permission to query activists") } if !UserHasRole("admin", authedUser) { // options.ChapterID == 0 means "do not filter by chapter", so this // check is important for security. if authedUser.ChapterID == 0 { return ActivistJSON{}, ValidationErrorf("cannot query activists without an active chapter") } options.ChapterID = authedUser.ChapterID } - return GetActivistJSON(db, options) + activists, err := GetActivistsExtra(db, options) + if err != nil { + return ActivistJSON{}, err + } + if len(activists) == 0 || activists[0].Hidden { + return ActivistJSON{}, errors.Wrapf(ErrNotFound, "could not find activist with id %d", options.ID) + } + if len(activists) > 1 { + return ActivistJSON{}, errors.Errorf("found too many activists with id %d", options.ID) + } + + return BuildActivistJSONArray(activists)[0], nil }🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@server/src/model/activist.go` around lines 581 - 596, GetActivistJSONForUser currently delegates to GetActivistJSON which may return hidden/merged activists; update GetActivistJSONForUser to enforce the API-only filter (a.hidden = false) by either setting a non-exported API flag or explicitly setting the options field that prevents hidden rows (e.g. options.Hidden = false or options.IgnoreHidden = false) before calling GetActivistJSON, or alternatively create a new GetActivistJSONPublic wrapper that applies the hidden=false filter and call that from GetActivistJSONForUser; ensure internal callers such as UserUpdateActivist continue to call the original GetActivistJSON so they can still load hidden rows.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@frontend-v2/src/app/`(authed)/activists/[id]/activist-detail.tsx:
- Around line 27-31: The loading check is conflating loading vs failed queries;
update the component to destructure isError and error from useActivist (e.g.,
const { data: activist, isLoading, isError, error } = useActivist(activistId))
and change the render logic so you only return the "Loading activist details..."
UI when isLoading is true; when isError or when !activist after loading, render
an error/fallback UI (e.g., show error?.message or a "Failed to load activist"
message) to surface failures instead of leaving the page stuck in the loading
state.
In `@frontend-v2/src/app/`(authed)/activists/activists-table.tsx:
- Around line 89-97: The link rendered inside the column check (colName ===
'name') uses the possibly empty value produced by formatValue(value, 'name'),
producing an unlabeled IntentPrefetchLink; change the render logic in
activists-table.tsx so that when formatted is falsy/empty you render a stable
fallback label (e.g. row.original.id or `Activist ${row.original.id}`) as the
link text and/or set an explicit aria-label using row.original.id, ensuring
IntentPrefetchLink remains accessible and never has an empty accessible name.
In `@frontend-v2/src/app/`(authed)/activists/format-value.ts:
- Around line 6-23: Precompute and cache column metadata at module scope to
avoid repeated Zod unwrapping and linear searches inside the hot path: build a
map from ActivistColumnName to its base type by iterating ActivistJSON.shape
once (using the same unwrapping logic now in getColumnType) and a map from
column name to its COLUMN_DEFINITIONS entry once (instead of repeated
COLUMN_DEFINITIONS.find calls); then update getColumnType and formatValue to
read from these cached maps (referencing getColumnType, formatValue,
COLUMN_DEFINITIONS, ActivistJSON, and ActivistColumnName) so each cell render
performs O(1) lookups only.
In `@frontend-v2/src/app/`(authed)/activists/linked-value.tsx:
- Around line 5-13: getLinkHref currently builds tel: and mailto: hrefs even
when value is an empty string; change getLinkHref to first treat
blank/whitespace-only values as absent (e.g., if value.trim() === '' return
null) and then construct the hrefs — specifically update the getLinkHref
function so the 'tel' and 'mailto' branches return null for blank values before
returning `tel:${value}` or `mailto:${value}` (you can keep the existing url
branch unchanged).
In `@server/src/main.go`:
- Around line 1111-1122: In EventGetHandler, avoid using http.Error (which
returns plain text) and instead write the API's JSON error envelope while
setting the HTTP status code: for the model.GetEvent call (using
model.GetEventOptions and checking model.ErrNotFound) set
w.Header().Set("Content-Type","application/json"), call w.WriteHeader with
either http.StatusNotFound or http.StatusInternalServerError, and encode a JSON
object like {"status": <code>, "message": "<human message>"} (use
json.NewEncoder(w).Encode) so clients receive the consistent {status,message}
shape instead of plain text.
---
Duplicate comments:
In `@server/src/model/activist.go`:
- Around line 581-596: GetActivistJSONForUser currently delegates to
GetActivistJSON which may return hidden/merged activists; update
GetActivistJSONForUser to enforce the API-only filter (a.hidden = false) by
either setting a non-exported API flag or explicitly setting the options field
that prevents hidden rows (e.g. options.Hidden = false or options.IgnoreHidden =
false) before calling GetActivistJSON, or alternatively create a new
GetActivistJSONPublic wrapper that applies the hidden=false filter and call that
from GetActivistJSONForUser; ensure internal callers such as UserUpdateActivist
continue to call the original GetActivistJSON so they can still load hidden
rows.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: a24bf291-61c1-4cb1-a567-3c00dde3992a
📒 Files selected for processing (31)
AGENTS.mdfrontend-v2/src/app/(authed)/activists/[id]/activist-detail.tsxfrontend-v2/src/app/(authed)/activists/[id]/loading.tsxfrontend-v2/src/app/(authed)/activists/[id]/page.tsxfrontend-v2/src/app/(authed)/activists/activists-table.tsxfrontend-v2/src/app/(authed)/activists/column-definitions.tsfrontend-v2/src/app/(authed)/activists/filter-api-transform.tsfrontend-v2/src/app/(authed)/activists/filter-url-codecs.tsfrontend-v2/src/app/(authed)/activists/filters/date-range-filter.tsxfrontend-v2/src/app/(authed)/activists/filters/int-range-filter.tsxfrontend-v2/src/app/(authed)/activists/format-value.tsfrontend-v2/src/app/(authed)/activists/linked-value.tsxfrontend-v2/src/app/(authed)/activists/page.tsxfrontend-v2/src/app/(authed)/coachings/[id]/page.tsxfrontend-v2/src/app/(authed)/events/[id]/page.tsxfrontend-v2/src/app/(authed)/interest/generator/page.tsxfrontend-v2/src/app/(authed)/intl/organizers/page.tsxfrontend-v2/src/app/(authed)/users/[id]/page.tsxfrontend-v2/src/app/(authed)/users/new/page.tsxfrontend-v2/src/app/(authed)/users/page.tsxfrontend-v2/src/app/not-found.tsxfrontend-v2/src/app/site-background-controller.tsxfrontend-v2/src/lib/api.tsfrontend-v2/src/lib/api/activists.tsfrontend-v2/src/lib/number-utils.tsfrontend-v2/src/lib/server-auth.tsserver/src/main.goserver/src/model/activist.goserver/src/model/activist_test.goserver/src/model/event.goserver/src/transport/activists.go
alexsapps
force-pushed
the
alex/view-activist
branch
from
f0325e2 to
a45be04
Compare
There was a problem hiding this comment.
Actionable comments posted: 2
♻️ Duplicate comments (1)
server/src/model/activist.go (1)
581-595:⚠️ Potential issue | 🟠 MajorHidden activists are still visible through the new detail endpoint.
This API-facing helper adds role and chapter checks, but it still delegates to the unrestricted ID lookup. Because that shared ID path does not filter
a.hidden, an organizer who knows an ID can fetch a hidden activist. Please enforce hidden=false at this boundary—without breaking internal callers likeUserUpdateActivistthat still need unrestricted ID lookups—e.g. by selecting the hidden flag and mapping hidden rows toErrNotFound.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@server/src/model/activist.go` around lines 581 - 595, GetActivistJSONForUser currently delegates to the unrestricted GetActivistJSON and thus leaks hidden activists; fix it by enforcing hidden=false at this API boundary: when preparing options in GetActivistJSONForUser (GetActivistOptions) ensure the query includes hidden=false (or explicitly select the hidden column and return ErrNotFound if the row has hidden==true) before returning the ActivistJSON so internal callers like UserUpdateActivist that rely on unrestricted ID lookups are not changed; reference GetActivistJSONForUser, GetActivistJSON, GetActivistOptions, UserUpdateActivist, and ErrNotFound when making the change.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@frontend-v2/src/lib/api.ts`:
- Around line 551-591: The current normalization only fills missing numeric
fields (via BLANK_TO_ZERO_FIELDS) but doesn't handle boolean fields that arrive
as undefined when the server omits false; add a boolean normalization pass:
introduce a BLANK_TO_FALSE_FIELDS (or similar) list, add a helper like
fillActivistBlankBooleanFieldsWithFalseForFields (mirroring
fillActivistBlankNumericFieldsWithZeroForFields) that sets undefined boolean
fields to false on an ActivistJSON, and call it from
fillSingleActivistBlankNumericFieldsWithZero and
fillActivistBlankNumericFieldsWithZero (apply both numeric and boolean helpers
when mapping activists), referencing the existing functions
fillActivistBlankNumericFieldsWithZeroForFields,
fillSingleActivistBlankNumericFieldsWithZero,
fillActivistBlankNumericFieldsWithZero and BLANK_TO_ZERO_FIELDS to locate where
to add the boolean handling.
In `@frontend-v2/src/lib/api/activists.ts`:
- Around line 5-6: The ActivistJSON Zod schema currently declares name as
optional; change it to a required string by replacing z.string().optional() with
z.string() in the ActivistJSON definition so the schema matches the backend
guarantee (keep id as z.number() unchanged); update any imports/usages if type
inference changes.
---
Duplicate comments:
In `@server/src/model/activist.go`:
- Around line 581-595: GetActivistJSONForUser currently delegates to the
unrestricted GetActivistJSON and thus leaks hidden activists; fix it by
enforcing hidden=false at this API boundary: when preparing options in
GetActivistJSONForUser (GetActivistOptions) ensure the query includes
hidden=false (or explicitly select the hidden column and return ErrNotFound if
the row has hidden==true) before returning the ActivistJSON so internal callers
like UserUpdateActivist that rely on unrestricted ID lookups are not changed;
reference GetActivistJSONForUser, GetActivistJSON, GetActivistOptions,
UserUpdateActivist, and ErrNotFound when making the change.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: 52a30e8e-e252-4ce1-a820-b28746ed216c
📒 Files selected for processing (31)
frontend-v2/src/app/(authed)/activists/[id]/activist-detail.tsxfrontend-v2/src/app/(authed)/activists/[id]/loading.tsxfrontend-v2/src/app/(authed)/activists/[id]/page.tsxfrontend-v2/src/app/(authed)/activists/activists-table.tsxfrontend-v2/src/app/(authed)/activists/column-definitions.tsfrontend-v2/src/app/(authed)/activists/filter-api-transform.tsfrontend-v2/src/app/(authed)/activists/filter-url-codecs.tsfrontend-v2/src/app/(authed)/activists/filters/date-range-filter.tsxfrontend-v2/src/app/(authed)/activists/filters/int-range-filter.tsxfrontend-v2/src/app/(authed)/activists/format-value.tsfrontend-v2/src/app/(authed)/activists/linked-value.tsxfrontend-v2/src/app/(authed)/activists/page.tsxfrontend-v2/src/app/(authed)/coachings/[id]/page.tsxfrontend-v2/src/app/(authed)/events/[id]/page.tsxfrontend-v2/src/app/(authed)/interest/generator/page.tsxfrontend-v2/src/app/(authed)/intl/organizers/page.tsxfrontend-v2/src/app/(authed)/users/[id]/page.tsxfrontend-v2/src/app/(authed)/users/new/page.tsxfrontend-v2/src/app/(authed)/users/page.tsxfrontend-v2/src/app/not-found.tsxfrontend-v2/src/app/site-background-controller.tsxfrontend-v2/src/lib/api.tsfrontend-v2/src/lib/api/activists.tsfrontend-v2/src/lib/number-utils.tsfrontend-v2/src/lib/server-auth.tsserver/src/main.goserver/src/model/activist.goserver/src/model/activist_test.goserver/src/model/event.goserver/src/transport/activists.goserver/src/transport/common.go
alexsapps
force-pushed
the
alex/view-activist
branch
from
a45be04 to
e589859
Compare
This was referenced Apr 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
read-only for now
Summary by CodeRabbit
New Features
Bug Fixes
Documentation
Tests