Skip to content

Conversation

@xitij2000
Copy link
Contributor

@xitij2000 xitij2000 commented Aug 12, 2021

This ADR proposes the mechanism for MFEs to get access to the discussion embed for units.

Depends/builds on: https://github.com/edx/edx-platform/pull/28221

@openedx-webhooks openedx-webhooks added blended PR is managed through 2U's blended developmnt program needs triage labels Aug 12, 2021
@openedx-webhooks
Copy link

openedx-webhooks commented Aug 12, 2021

Thanks for the pull request, @xitij2000! I've created BLENDED-939 to keep track of it in Jira. More details are on the BD-38 project page.

When this pull request is ready, tag your edX technical lead.

Copy link
Contributor

@arjunsinghy96 arjunsinghy96 left a comment

Choose a reason for hiding this comment

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

👍 @xitij2000 LGTM. I have suggested a couple of minor nits. Could you please look at them before moving forward?

  • I tested this: (describe what you tested)
  • I read through the code
  • I checked for accessibility issues
  • Includes documentation
  • I made sure any change in configuration variables is reflected in the corresponding client's configuration-secure repository.

@xitij2000 xitij2000 force-pushed the kshitij/tnl-8396/discussions-course-blocks branch 3 times, most recently from 6113bf3 to d3a1f89 Compare September 14, 2021 13:03
This ADR proposes the mechanism for MFEs to get access to the discussion embed for units.
@xitij2000 xitij2000 force-pushed the kshitij/tnl-8396/discussions-course-blocks branch from d3a1f89 to cda4d0e Compare September 14, 2021 13:10
@xitij2000
Copy link
Contributor Author

@awaisdar001 I have updated the ADR. Please have another look.

For units that don't have a linked discussion, no link will be returned.

The new discussions experience includes a setting called
`discussions_group_at_subsection` to group discussions at the subsection
Copy link
Contributor

Choose a reason for hiding this comment

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

Is the discussion MFE is the provider of this setting? How this setting is turned on or off?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think the previous ADR is good reference for this.

It's a setting stored in the course structure and will be configurable using an API, and using the course authoring MFE. You can see these in the figma mockup.

Copy link
Contributor

Choose a reason for hiding this comment

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

got it

The new discussions experience includes a setting called
`discussions_group_at_subsection` to group discussions at the subsection
level instead of the unit level. Normally the sidebar next to a unit will
only show threads from that unit. However, if this setting is enabled
Copy link
Contributor

Choose a reason for hiding this comment

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

if this setting is enabled => Yes - Same question, how this setting is enabled/disabled?

Copy link
Contributor Author

Choose a reason for hiding this comment

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


The new discussions experience includes a setting called
`discussions_group_at_subsection` to group discussions at the subsection
level instead of the unit level. Normally the sidebar next to a unit will
Copy link
Contributor

Choose a reason for hiding this comment

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

by Normally do you mean when the discussions_group_at_subsection setting is off/disabled?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes.

Decision
--------

A direct link to the topic that needs to be embedded can be generated
Copy link
Contributor

Choose a reason for hiding this comment

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

You said that "a direct link to the topic" will be provided by edx-platform using the course blocks API, but when you access the API using requested_fields=discussions_embed_url, it returns an object with different kinds of URLs.

Can specify which is the embeddable URL among those when you call it "a direct link"?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is just the standard default response of the course blocks API. It returns some standard fields, and other fields can be requested in addition as needed.

In this case, the idea is to add a new field option as specified above and have that add a new return value called "discussions_embed_url". I've cleaned up some the other URLs so it's easier to focus on this new field.

Copy link
Contributor

Choose a reason for hiding this comment

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

Ok, taking a look.

@edx-status-bot
Copy link

Your PR has finished running tests. There were no failures.

@awaisdar001 awaisdar001 merged commit a35fa08 into openedx:master Sep 17, 2021
@openedx-webhooks
Copy link

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

@edx-pipeline-bot
Copy link
Contributor

EdX Release Notice: This PR has been deployed to the staging environment in preparation for a release to production.

@edx-pipeline-bot
Copy link
Contributor

EdX Release Notice: This PR has been deployed to the production environment.

@xitij2000 xitij2000 deleted the kshitij/tnl-8396/discussions-course-blocks branch September 20, 2021 05:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

blended PR is managed through 2U's blended developmnt program merged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants