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

feat: create a new setting USE_DISCUSSIONS_MFE (#809) #828

Closed
wants to merge 1 commit into from

Conversation

dcoa
Copy link

@dcoa dcoa commented Aug 7, 2024

This is a backport of the Flag for enable/disable discussions MFE by tenant

* feat: create a new setting USE_DISCUSSIONS_MFE

* feat: add new setting USE_DISCUSSIONS_MFE

* fix: quality checks

* fix: add setting override

* fix: add setting override

* fix: add setting override

* fix: pep 8 violations

* fix: update setting name

Co-authored-by: Brayan Cerón <[email protected]>

* fix: change variable name

---------

Co-authored-by: Brayan Cerón <[email protected]>
@dcoa dcoa requested review from MaferMazu, mariajgrimaldi, bra-i-am and a team August 7, 2024 12:22
True if the MFE setting is activated, by default
the MFE is deactivated
"""
ENABLE_MFE_FOR_TESTING = SettingDictToggle(
Copy link
Contributor

@magajh magajh Aug 7, 2024

Choose a reason for hiding this comment

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

Maybe I'm missing some context here, but is there a particular reason why this setting is named ENABLE_MFE_FOR_TESTING? The name doesn't specify that it's for the Discussions MFE, and including the word 'testing' also seems out of place

@mariajgrimaldi
Copy link
Member

Is there a reason we'd want to disable the discussions MFE by tenant? Can we explain it in the cover letter? Thanks!

@dcoa
Copy link
Author

dcoa commented Aug 8, 2024

I will close this understanding we decided to use edx-platform as upstream is.

@dcoa dcoa closed this Aug 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants