Skip to content
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

fix: replace Field.Email reference for Field.Text #345

Merged
merged 1 commit into from
Sep 25, 2023

Conversation

dcoa
Copy link
Contributor

@dcoa dcoa commented Aug 7, 2023

Description
The master branch doesn't have the references to new Field.Text updated, there is a screenshot of the error

image

As well useGradeButtonData doesn't return a string in the label field is returning a function, so the numbers weren't render
image

This PR tries to solve that rendering situation.

What changed?

  • Update the reference for Field.Email to Field.Text
  • Update the test.

Developer Checklist

  • Test suites passing
  • Documentation and test plan updated, if applicable
  • Received code-owner approving review
  • Bumped version number package.json

Reviewer Checklist

Collectively, these should be completed by reviewers of this PR:

  • I've done a visual code review
  • I've tested the new functionality

FYI: @openedx/content-aurora

@dcoa dcoa requested a review from a team as a code owner August 7, 2023 16:02
@openedx-webhooks openedx-webhooks added the open-source-contribution PR author is not from Axim or 2U label Aug 7, 2023
@openedx-webhooks
Copy link

openedx-webhooks commented Aug 7, 2023

Thanks for the pull request, @dcoa! Please note that it may take us up to several weeks or months to complete a review and merge your PR.

Feel free to add as much of the following information to the ticket as you can:

  • supporting documentation
  • Open edX discussion forum threads
  • timeline information ("this must be merged by XX date", and why that is)
  • partner information ("this is a course on edx.org")
  • any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.

Please let us know once your PR is ready for our review and all tests are green.

@codecov
Copy link

codecov bot commented Aug 7, 2023

Codecov Report

Patch coverage: 100.00% and no project coverage change.

Comparison is base (44197f6) 94.93% compared to head (e10ef6d) 94.93%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #345   +/-   ##
=======================================
  Coverage   94.93%   94.93%           
=======================================
  Files         139      139           
  Lines        1343     1343           
  Branches      264      264           
=======================================
  Hits         1275     1275           
  Misses         60       60           
  Partials        8        8           
Files Changed Coverage Δ
src/components/GradesView/GradebookTable/hooks.jsx 100.00% <ø> (ø)
...mponents/GradesView/GradebookTable/GradeButton.jsx 100.00% <100.00%> (ø)

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@mphilbrick211 mphilbrick211 added the waiting for eng review PR is ready for review. Review and merge it, or suggest changes. label Aug 8, 2023
@arslanashraf7
Copy link

Hey @mphilbrick211 we are facing the same issue while running the gradebook locally and on a server. Is it possible by any chance that the review on this PR could be prioritized?

@mphilbrick211
Copy link

Hey @mphilbrick211 we are facing the same issue while running the gradebook locally and on a server. Is it possible by any chance that the review on this PR could be prioritized?

Hi @openedx/content-aurora! Flagging this - would someone be able to please review?

@dcoa
Copy link
Contributor Author

dcoa commented Sep 12, 2023

@muselesscreator @leangseu-edx

Hi folks, could you help us with a review in his PR or help us identify the right reviewer?

Copy link
Contributor

@arbrandes arbrandes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changes make sense, but I'm worried the bugs they fix weren't caught by any tests to begin with. Would it be too much to ask to add some tests that would've done so?

@dcoa
Copy link
Contributor Author

dcoa commented Sep 24, 2023

Hi @arbrandes thank you for your review and not 100% sure to understand your request because when I used the branch I realized that the reason why the test didn't catch the errors was because the testing for this component and function was correct: Field.Text test and subsectionGrade test only the reference was not updated and not fail because of the use of jest.mock.

I updated the test reference too, or I just can think of using the original component instead of mocking it but that does not make the test fail only displays a console.error

@arbrandes
Copy link
Contributor

Yeah, it might be going overboard to test for this retroactively, here. I feel like it would initiate a full revamp, which would probably be better planned elsewhere. (As part of the migration to react-testing-library, perhaps.) Let's just fix the glaring issue and move on, for now.

@arbrandes arbrandes merged commit 1c70458 into openedx:master Sep 25, 2023
5 checks passed
@openedx-webhooks
Copy link

@dcoa 🎉 Your pull request was merged! Please take a moment to answer a two question survey so we can improve your experience in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
open-source-contribution PR author is not from Axim or 2U waiting for eng review PR is ready for review. Review and merge it, or suggest changes.
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

5 participants