-
Notifications
You must be signed in to change notification settings - Fork 86
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
feat: add open managed group type #669
Conversation
Thanks for the pull request, @Ian2012! 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. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #669 +/- ##
==========================================
+ Coverage 90.94% 91.30% +0.36%
==========================================
Files 520 561 +41
Lines 9157 9767 +610
Branches 1920 2081 +161
==========================================
+ Hits 8328 8918 +590
- Misses 797 816 +19
- Partials 32 33 +1 ☔ View full report in Codecov by Sentry. |
Hi @openedx/teaching-and-learning! This is ready for your review. Thanks! |
I've created issue TNL-11193 in the private 2U Jira. |
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.
Can we reorder the list so that "Open Managed" is between "Open" and "Public Managed"?
I think it makes sense since it creates a progression from fully open to fully private.
d4b586d
to
fae018c
Compare
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.
PR LGTM
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 again. I think this is good.
This should be merged after edx-platform/pull/33672, right?
Yes, it should. Waiting on review there |
68ed4e5
to
51687ad
Compare
51687ad
to
2213926
Compare
@Ian2012 sorry to come up so late with this request but to be extra safe when merging this. Could you please leave this feature behind a feature flag? CC @mariajgrimaldi in case you are taking over this feature. |
Hi there @felipemontoya, that's precisely what I did in this PR: #801, but I'll cherry-pick the changes here since they're needed. Thank you. |
@felipemontoya: done! Could you review this again? Thanks! |
I can't update the cover letter, so I leave here the updated testing instructions:
|
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.
Thanks a lot for moving this behind a flag @mariajgrimaldi.
I re-tested this today. The code is working on a tutor based environment together with the changes of the platform that were merged on PR 33672.
I think this is ready to be merged.
- it has product approval
- it has a core committer approval and 2 approvals by the 2u team.
- tests are running and passing
- the feature includes it's own tests
- the feature is behind a flag that is switched off by default. This won't impact edx.org's operation in any way.
@arbrandes or @brian-smith-tcril could one of you help us get the green button pushed? There is no backstage catalog file so I don't know who to flag as the maintainer. |
@felipemontoya, I'll be glad to, but my first question is: has this received product approval, yet? Tagging @jmakowski1123 preemptively. |
Sandbox deployment successful 🚀 |
Great! sandboxes are working. I don't know how to access that sandbox as an instructor user, and also I don't know how to make sure that the settings are complete, but overall I love sandboxes. |
Sandbox deployment failed 💥 |
@felipemontoya, custom settings are at the top of the PR description. There's docs at https://gitlab.com/opencraft/dev/grove/-/blob/main/docs/user-guides/automated-pr-sandbox.md and at https://gitlab.com/opencraft/dev/tutor-contrib-grove. I'll send you access details off-band. |
4215a51
to
86115c2
Compare
Fixed branch conflicts just now. |
Sandbox deployment failed 💥 |
I'll be fixing the failing tests soon; thanks for the patience. |
Sandbox deployment failed 💥 |
Sandbox deployment successful 🚀 |
Hello @arbrandes! This is ready for review if you have the time. Thanks! |
@mariajgrimaldi, in the sandbox, I can't configure Teams as instructed in the the backend PR. Any idea why that might be? A missing configuration item, perhaps? |
@arbrandes: I'll look into it! |
@arbrandes: could you share the access details for the sandox? Thanks! |
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.
Works great! Just one nit.
|
||
test('returns false if the group is invalid', () => { | ||
getConfig.mockReturnValue({ ENABLE_OPEN_MANAGED_TEAM_TYPE: true }); | ||
expect(isGroupTypeEnabled('')).toBe(false); |
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.
I'd feel safer if you made this an actual bogus value. Like:
expect(isGroupTypeEnabled('')).toBe(false); | |
expect(isGroupTypeEnabled('FOO')).toBe(false); |
@arbrandes: done! Thank you |
Sandbox deployment successful 🚀 |
@Ian2012 🎉 Your pull request was merged! Please take a moment to answer a two question survey so we can improve your experience in the future. |
Settings
Description
This PR adds support for the new open managed group type. Ref: https://openedx.atlassian.net/wiki/spaces/COMM/pages/3885760525/Open+Managed+Group+Type
Screenshots
Dependencies:
Depends on: openedx/edx-platform#33672