Merged
Conversation
fix: fixes some shrink problems
Mewbi
requested changes
May 2, 2024
Member
Mewbi
left a comment
There was a problem hiding this comment.
Missing break-all in retrospective description.
Suggestion to input limits
30 to 10 use text-gray-300
10 to 0 use text-red-500 and add a bounce animation to each character typed.
e0474e3 to
71471da
Compare
Mewbi
approved these changes
May 5, 2024
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
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.
In this PR, a couple of things were made. Here are what we did:
/api/limitsto get all limits. The response body expects the following schema:If the requests gets a 404 response, it uses the current API values, hardcoded in client. With this we can deploy the front even without a backend deploy