added working /apply form (no backend yet, just alerts) #3
Conversation
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
Generate a static site to allow deployment to Cloudflare Pages
❌ Deploy Preview for ciris failed. Why did it fail? →
|
ncheaz
approved these changes
Apr 24, 2025
Contributor
ncheaz
left a comment
ncheaz
left a comment
There was a problem hiding this comment.
The "prompt is not defined" error will be addressed in a separate PR so as to not hold off this change.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
This adds a working
/applypage using the App Router. It’s fully client-side for now and doesn’t connect to any backend — it just alerts the form data on submit.Form fields:
There’s no external API usage. I originally had a GitHub autofill feature but pulled it out to keep the page static-export safe.
Form state is handled with
useState, and there's a submit handler already scoped for future POST logic (like/api/applyor whatever backend we use later).Tested with
npm run dev— works fine.Tried
next export, but it failed due to an unrelated type error in[[...slug]]/page.tsx. This file is export-safe if isolated.Let me know if you want this wired up to a real endpoint, or if I should add more fields or clean anything else up.
– Brad