London | 26-SDC-March | Zobeir Rigi | Legacy-Code |Sprint 1 | Enforce 280 character limit for blooms#250
Open
Zobeir-Rigi wants to merge 1 commit into
Open
Conversation
Zobeir-Rigi
added
📅 Sprint 1
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.
Bug
Blooms longer than 280 characters could be posted even though blooms are intended to be limited to 280 characters.
Fix
Added backend validation to reject blooms that exceed the 280-character limit before they are saved.