Fixed Founder's Club references #130
Conversation
|
@yatinannam is attempting to deploy a commit to the fc-temp Team on Vercel. A member of the Team first needs to authorize it. |
There was a problem hiding this comment.
Pull request overview
Updates “Founder's Club” branding references across Supabase email functions and the Next.js UI.
Changes:
- Updated sender/from names and visible UI strings from “Founder's Club” to “Founders Club”.
- Adjusted contact email template/signature text to use the updated branding.
- Reformatted some TS/TSX files (notably switching to double quotes in places).
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 11 comments.
Show a summary per file
| File | Description |
|---|---|
| supabase/functions/event-rejection-email/index.ts | Updates sender display name for rejection emails. |
| supabase/functions/contact-function/template.ts | Updates branding text in the contact confirmation email template. |
| supabase/functions/contact-function/index.ts | Updates sender display name and branding text in support notification email content. |
| src/components/upcoming-featured.tsx | Updates “Founder's Club” UI strings/alt text for the featured upcoming event card. |
| src/app/(home)/upcoming/more-info/[slug]/page.tsx | Updates “Founder's Club” UI strings/alt text on the event details page. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| import { formatInTimeZone } from "date-fns-tz"; | ||
| import { ArrowUpRight, CalendarX2 } from "lucide-react"; | ||
| import Image from "next/image"; | ||
| import Link from "next/link"; | ||
| import { Badge } from "@/components/ui/badge"; | ||
| import { Button } from "@/components/ui/button"; |
There was a problem hiding this comment.
This file now uses double-quoted string literals, but the repo’s Biome config sets javascript.formatter.quoteStyle to single. Please revert these to single quotes (or run the Biome formatter) to avoid style drift/noisy diffs.
| ); | ||
| } | ||
| const tags = event.tags.map(tag => ( | ||
| const tags = event.tags.map((tag) => ( |
There was a problem hiding this comment.
event.tags.map((tag) => ...) adds parentheses around a single-arg arrow function; Biome is configured with arrowParentheses: asNeeded, so this should be tag => ... to match the repo formatter.
| const tags = event.tags.map((tag) => ( | |
| const tags = event.tags.map(tag => ( |
| @@ -129,10 +127,10 @@ export function FeaturedPost({ event }: { event: eventsInsertType }) { | |||
| <div className="flex flex-col gap-px"> | |||
| <span className="text-xs font-medium">Founder's Club</span> | |||
There was a problem hiding this comment.
This section still renders the label as "Founder’s Club" while other updated strings in this component use "Founders Club". Update this remaining UI string so the branding is consistent across breakpoints.
| <span className="text-xs font-medium">Founder's Club</span> | |
| <span className="text-xs font-medium">Founders Club</span> |
| content={ | ||
| <div className="flex flex-wrap gap-2"> | ||
| {event.tags.map(tag => ( | ||
| {event.tags.map((tag) => ( |
There was a problem hiding this comment.
event.tags.map((tag) => ...) adds parentheses for a single-parameter arrow function, which conflicts with the repo’s arrowParentheses: asNeeded setting. Prefer tag => ... here.
| {event.tags.map((tag) => ( | |
| {event.tags.map(tag => ( |
| const senderEmailData = { | ||
| from: "The Founder's Club <no-reply@thefoundersclub.tech>", | ||
| from: "The Founders Club <no-reply@thefoundersclub.tech>", | ||
| to: [record.email], | ||
| subject: 'Your Contact Request has been Submitted', | ||
| html: generateHTML(record), |
There was a problem hiding this comment.
The from value uses double quotes, while the rest of the file uses single quotes. Please change to single quotes to keep formatting consistent and avoid formatter churn.
| <td class="pad" style="padding-left:38px;padding-right:38px;padding-top:10px;"> | ||
| <div style="color:#000000;font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;line-height:150%;;mso-line-height-alt:24px;"> | ||
| <p style="margin: 0;"><span style="word-break: break-word; color: #4b4949;">Hello ${record.name},</span><br><br><span style="word-break: break-word; color: #4b4949;">Thank you for reaching out to the Founder's Club! We have successfully received your contact request and will be shortly reaching out to you.<br/><br/>The Founder's Club<br/>Directorate of Entrepeunership and Innovation<br/>SRM Institute of Science and Technology<br/>Kattankulathur<br/>Tamil Nadu - 603203</span></p> | ||
| <p style="margin: 0;"><span style="word-break: break-word; color: #4b4949;">Hello ${record.name},</span><br><br><span style="word-break: break-word; color: #4b4949;">Thank you for reaching out to the Founders Club! We have successfully received your contact request and will be shortly reaching out to you.<br/><br/>The Founders Club<br/>Directorate of Entrepeunership and Innovation<br/>SRM Institute of Science and Technology<br/>Kattankulathur<br/>Tamil Nadu - 603203</span></p> |
There was a problem hiding this comment.
Email template text contains a misspelling: "Entrepeunership" should be "Entrepreneurship" (user-facing email content).
| <p style="margin: 0;"><span style="word-break: break-word; color: #4b4949;">Hello ${record.name},</span><br><br><span style="word-break: break-word; color: #4b4949;">Thank you for reaching out to the Founders Club! We have successfully received your contact request and will be shortly reaching out to you.<br/><br/>The Founders Club<br/>Directorate of Entrepeunership and Innovation<br/>SRM Institute of Science and Technology<br/>Kattankulathur<br/>Tamil Nadu - 603203</span></p> | |
| <p style="margin: 0;"><span style="word-break: break-word; color: #4b4949;">Hello ${record.name},</span><br><br><span style="word-break: break-word; color: #4b4949;">Thank you for reaching out to the Founders Club! We have successfully received your contact request and will be shortly reaching out to you.<br/><br/>The Founders Club<br/>Directorate of Entrepreneurship and Innovation<br/>SRM Institute of Science and Technology<br/>Kattankulathur<br/>Tamil Nadu - 603203</span></p> |
| import { formatInTimeZone } from "date-fns-tz"; | ||
| import { CalendarDays, Clock, Info, MapPin, Tag, User } from "lucide-react"; | ||
| import type { Metadata, ResolvingMetadata } from "next"; | ||
| import Image from "next/image"; | ||
| import Link from "next/link"; | ||
| import { Badge } from "@/components/ui/badge"; | ||
| import { Button } from "@/components/ui/button"; |
There was a problem hiding this comment.
This file switches many literals/imports to double quotes, but the repo’s Biome config enforces single quotes (javascript.formatter.quoteStyle: single). Please run the formatter or revert to single quotes to keep consistent styling and avoid churn.
| // Send confirmation email to registrant | ||
| const registrantEmailData = { | ||
| from: "The Founder's Club <no-reply@thefoundersclub.tech>", | ||
| from: "The Founders Club <no-reply@thefoundersclub.tech>", |
There was a problem hiding this comment.
The from field is the only string here using double quotes in a file otherwise consistently using single quotes. For consistency (and to match the Biome quoteStyle setting), switch this to single quotes.
| from: "The Founders Club <no-reply@thefoundersclub.tech>", | |
| from: 'The Founders Club <no-reply@thefoundersclub.tech>', |
| const supportEmailData = { | ||
| from: "The Founder's Club <no-reply@thefoundersclub.tech>", | ||
| from: "The Founders Club <no-reply@thefoundersclub.tech>", | ||
| to: ['support@thefoundersclub.in'], |
There was a problem hiding this comment.
The from value here also uses double quotes in an otherwise single-quote file; please switch to single quotes to match repo formatting.
| // Send confirmation email to registrant | ||
| const registrantEmailData = { | ||
| from: "The Founder's Club <no-reply@thefoundersclub.tech>", | ||
| from: "The Founders Club <no-reply@thefoundersclub.tech>", | ||
| to: [record.registration_email], | ||
| subject: 'Your Event Registration Confirmation', | ||
| html: generateHTML(record), |
There was a problem hiding this comment.
This function only sends when is_approved === 'REJECTED', but the inline comment and email subject still say “confirmation”. That’s likely to confuse recipients and doesn’t match the rejection template content; update the subject (and comment) to indicate rejection.
No description provided.