-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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: course mode added to the metadata #33690
fix: course mode added to the metadata #33690
Conversation
Thanks for the pull request, @Inferato! 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:
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. |
Hi there @dyudyunov! Regarding your comment here, is this something you folks are still going to pursue? |
I'll find time to search and inspect all the PRs Taras has made. |
Sorry for all the pings. Thank you @dyudyunov! |
Hi there @mariajgrimaldi I checked this fix and it is actual. I would like to add a bit more context to the problem. The Communication MFE has course mode checkboxes hardcoded, so a user can select any of them even if the course has no such mode. The goal here is to provide course mode checkboxes for real course modes only. This PR seems to be ready for the review. |
I can't update Taras' source branch, so I created a new related PR to the Communications MFE. It consists of the original commits plus Adolfo's suggestions applied in a separate one. |
I understand this is a fix of the current behavior, but since this changes how the communications MFE behaves I added the product review label. |
@mariajgrimaldi hi! Related PR to the Communications MFE was just merged, but it requires this one to work properly Is it possible to prioritize this PR to avoid problems with the Communications MFE? @arbrandes this is my fault, I mentioned the related Communications MFE PR here but forgot to add the note about the dependency in the Communications MFE PR |
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.
This change makes sense, and as @dyudyunov put it, it is required for the Communications MFE to work as it stands in master now.
I submit that this is actually a bug fix, so no product review required.
I'm not a CC here so can't approve. @kdmccormick or @feanil, any objections to merging it?
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 good to me, it's adding more data to an existing API endpoint and the lookup should be pretty cheap so not a performance concern either.
@dyudyunov should I go ahead and merge this or are there any reasons to hold-off? |
@Inferato 🎉 Your pull request was merged! Please take a moment to answer a two question survey so we can improve your experience in the future. |
2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production. |
2U Release Notice: This PR has been deployed to the edX production environment. |
Description
According to the chapter Sending Email Messages to Learners in Different Enrollment Tracks course can may more than one mode and instructor must have the ability to send the email for users in this modes.
Communication MFE had a hardcoded 2 modes for every course. Sometimes it lead to the error.
courseModes
was added tocourseMetadata
to display real course email recipient options.Related MR:
Deadline
None