Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
jaykbpark
force-pushed
the
agent/allow-empty-partner-description
branch
from
September 7, 2026 23:05
285c244 to
3c59e07
Compare
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.
What changed
Why
Create and edit payloads already send
partnerDescriptionas a string and support"", but the frontend schema blocked saving unless the field contained text.Impact
Events without partner-specific copy can be saved while preserving the backend field.
Validation
""npm run lint(passes with pre-existing warnings)git diff --check