Feat/careers - #1
Merged
Merged
Conversation
Three open roles live as data in lib/careers/roles.ts rather than the database: a job post is content that ships with a deploy and wants review in a pull request, and there are three of them. The database side is only the inbound applications, which is the part that actually grows. /careers lists the roles; /careers/[slug] renders the full JD and the application form (name, email, message to the recruiter, an explicit permission checkbox). Role pages are prerendered and carry JobPosting JSON-LD so they can surface in Google's job results. The zod schema in lib/careers/application.ts is shared by the form and the route, so the browser and the server cannot disagree about what a valid application looks like. The route is still the authority and re-validates everything. job_applications has no users reference: an applicant is almost never a signed-in user, and nothing here should cascade from an account deletion. role_title is a snapshot of the title as advertised, so a later retitle cannot rewrite what someone believes they applied for. The route dedupes per email per role over 24 hours and reports success on a repeat rather than an error, since the applicant already told us. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Naki3DJALSYSKgZLkEjuYU
.env.local and .env.production.local were both reachable by the old rule only if you remembered to add them. The tracked .env.example and .env.docker stay tracked; a broadened ignore does not untrack a file git already knows about. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Naki3DJALSYSKgZLkEjuYU
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.
No description provided.