-
-
Notifications
You must be signed in to change notification settings - Fork 0
feat(studio): add taskDescription
to person.affiliations
#108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
WalkthroughThe changes introduce a new field, Changes
Assessment against linked issues
Possibly related PRs
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (3)
apps/studio/schemas/documents/person.ts (3)
53-63
: LGTM! Consider implementing validation rules.The new
taskDescription
field has been successfully added to theaffiliations
array, aligning with the PR objectives. The field description provides clear guidance on the expected content and length.Consider uncommenting and implementing the validation rules to enforce the specified character limit (270 to 330 characters). This will ensure data consistency and adherence to the description guidelines.
69-69
: LGTM! Consider implementing validation rules.The description for the
description
field has been successfully updated to reflect its new purpose as a vision statement for the person, which aligns with the changes mentioned in the AI-generated summary.Consider uncommenting and implementing the validation rules to enforce the specified character limits (32 to 200 characters). This will ensure data consistency and adherence to the description guidelines.
53-69
: Overall implementation looks good. Consider adding translations.The changes successfully implement the new
taskDescription
field and update thedescription
field as per the PR objectives. Both fields now provide clear guidance on their purpose and expected content.Given that the field titles and descriptions are in German, consider implementing internationalization for these strings to support multiple languages in the future. This could be done using a translation library or Sanity's built-in localization features.
closes #106
Summary by CodeRabbit
New Features
taskDescription
, in the affiliations section of the person document to allow for brief task descriptions related to a person's position.Updates
description
field to clarify its purpose as a short vision of the person.