feat: hackathon submission - tag subscriber in kit #63
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
- Introduced a new section to display active hackathons associated with episodes, including title, deadline, sponsors, and a join button. - Updated the episode schema to include hackathon data retrieval. - Enhanced styling for the new hackathon card layout to improve visual presentation.
- Added new Kit integration with schema and steps for tagging subscribers. - Updated client and index files to include Kit schemas and functions. - Enhanced website integration to invoke the new tag subscriber function during relevant workflows. - Improved error handling and response structure in the Kit API functions.
- Removed console log from the tagSubscriber function. - Updated the tagSubscriber function to throw an error if tagName is not provided. - Changed the parameter used in the tagSubscriberKit function call from tag to tagName for consistency.
- Eliminated the 'log-the-output' step from the hackathon submission process to streamline the workflow. - This change enhances the clarity and efficiency of the integration without affecting functionality.
👷 Deploy request for codetv-automations pending review.Visit the deploys page to approve it
|
👷 Deploy request for codetv pending review.Visit the deploys page to approve it
|
✅ Deploy Preview for codetv-links ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
jlengstorf
reviewed
Jan 8, 2026
Contributor
jlengstorf
left a comment
jlengstorf
left a comment
There was a problem hiding this comment.
looking great! I have one open question but I think this is looking good to go
| step: any; | ||
| }): Promise<{ subscription: any }> { | ||
| return await step.run('tag-subscriber', async () => { | ||
| return await tagSubscriberKit(event.data.email, event.data.tagName); |
Contributor
There was a problem hiding this comment.
I might be staring right at it, but what happens if this email is not subscribed? we probably need to check for that kind of failure and signal that it's non-retriable so Inngest doesn't keep retrying
Co-authored-by: Jason Lengstorf <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
No description provided.