Standardize and update field length constraints#3293
Draft
Conversation
- standardize string field length limits across the codebase by introducing centralized constants and annotated types, ensuring consistent validation between frontend and backend - rename UpdateCrawlConfig to CrawlConfigUpdate for consistency with other update model names - update front-end validation logic to reflect back-end changes in a few places
- replace str with OrgPublicDescription in both Org and OrgReadCreate models - increase org description max length from 150 to 400 characters to match backend
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.
introducing centralized constants and annotated types, ensuring
consistent validation between frontend and backend
other update model names
places