-
Notifications
You must be signed in to change notification settings - Fork 5
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
Issue #144 | 1 test failed, but works as expected. #147
Issue #144 | 1 test failed, but works as expected. #147
Conversation
…o changing routes)
Reviewing why the eslint error occured. |
…ld ver. Works now.)
I am very sorry as I am not getting where is the error coming from.
|
Hey! Thanks so much for working on this; looks like a good first pass! 🚀
This actually isn't quite what I had in mind for the update - which is not your fault; totally on me for not including more info in the issue, so I'll try to do better with that in the future. Here's a mockup of more what I had in mind: So removing the contact form entirely in favor of a link that would take the user (in a new tab) to https://github.com/blackjackkent/RPThreadTrackerV3.FrontEnd/issues/new
The testing issue is with a Jest snapshot that needs to be updated. Some of the tests in the Tracker codebase make use of Jest snapshot testing to help ensure that no components change their appearance in a way that we don't expect. You can learn more about it here: https://jestjs.io/docs/en/snapshot-testing I'm happy to help further explain if this is confusing but check out those docs first and see if it helps. :) |
Ahhhhh, It makes sense now haha. Sorry couldn't get what you meant in the beginning, I get it now! Thank you!. I'll dive back into it rn and try to do it the way you wanted it. Thank you for clearing up! |
Please do check now as I did it similar to the Mockup. Clicking on the button redirects you to the Github new issue page. But, sorry couldn't fix the snapshot thingy. Sorry about that. Other than that, did what was asked. Please do a review. And thank you for the opportunity!. |
src/display/views/help/components/__tests__/ContactFormPane.spec.js
Outdated
Show resolved
Hide resolved
Thanks again so much for contributing! :D I've left some comments about things that can be adjusted - mainly that this doens't need to be a form submission anymore and can just be a link. If you want to dive deeper, you can also remove other references to the |
Fixed whats was asked after reviews. Please do take a look and let me know if there's more to change. Sorry for not understanding clearly earlier, and if there is more to change please do let me know. I'll try my best to resolve it. Thank you very much for pointing out the errors I made, will keep it in mind when doing something similar. Learned lots of things from this project, this PR in particular. Thank you for this opportunity! |
Feels good to see "All checks have passed". Ahh, Thank you again! |
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.
Revied the changes asked and did a new PR on it (This comment should go up, forgot to "Comment on Review" earlier. (Sorry)
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.
Looks great! Much cleaner. :) I marked a few small typos that need to be cleaned up.
Not required, but since there's no state being managed in ContactFormPane
anymore, you could refactor it to a functional component rather than a class one. :) If you don't want to work on that right now, we can just merge this, though. I only mention it in case you want ideas for other stuff to do. :D
src/display/views/help/components/__tests__/__snapshots__/ContactFormPane.spec.js.snap
Outdated
Show resolved
Hide resolved
src/display/views/help/components/__tests__/__snapshots__/ContactFormPane.spec.js.snap
Outdated
Show resolved
Hide resolved
Also, that |
Ahh thanks for pointing them out, will do that instantly! |
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.
Reviewed, and edited them on my vs. Commiting soon
Done. Fixed after review. Please do let me know if there's anything left. Thank you! |
Looks like you need to fix the snapshot again since you updated the text in the component. :) Otherwise, this looks good! |
Will do that rn haha mbmb |
Codecov Report
@@ Coverage Diff @@
## development #147 +/- ##
================================================
+ Coverage 0 99.15% +99.15%
================================================
Files 0 287 +287
Lines 0 3205 +3205
Branches 0 588 +588
================================================
+ Hits 0 3178 +3178
- Misses 0 27 +27
Continue to review full report at Codecov.
|
Title
Issue #144 | 1 test failed but works as expected. Ran tests, 1 failed cause it was related to the old routing, not the latest one.
Description
I changed the path of routings to be redirected to the new issue page instead of emails, as asked.
Motivation and Context
It was asked as an issue and I was interested in working on this as apart of my coursework and self-practice. I thank the person for assigning me this task.
How Has This Been Tested?
The code has been tested. It came out with one testing error (ass expected). It is due to the fact that I changed the routing to a different site, the testing was for the old path (the email).
Screenshots (if appropriate):
Types of changes
Checklist: