1245 Input testing #1491
Merged
1245 Input testing #1491
Conversation
This file contains 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
Closed
16 tasks
sydneywalcoff
force-pushed
the
1245-input-testing
branch
from
7071444 to
e7e03c9
Compare
|
@sydneywalcoff figured out the config file to get the console warnings to disappear 🎉 |
sydneywalcoff
approved these changes
Oct 8, 2024
There was a problem hiding this comment.
@eburdekin YAY! Thank you for digging around with this and figuring out a solution. I really didn't know what to do with this lol.
sydneywalcoff
approved these changes
Oct 8, 2024
There was a problem hiding this comment.
@eburdekin YAY! Thank you for digging around with this and figuring out a solution. I really didn't know what to do with this lol.
lol why did this post twice
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.
Fixes #1245
Changes made:
Added tests for the following:
Reason for changes:
We want to retroactively implement testing to better protect our codebase
@sydneywalcoff I tried setting up a jest config file to ignore these console warnings but couldn't quite figure it out. Could you help point me in the right direction?