• #517 is an empty commit but fails nevertheless.

STR:

1. Create a post
2. Create a response in this post
3. Hover on the response (will see the additional menu with add a comment, like, etc.)
4. Hover "Add comment"
5. Hover "like"
6. Observe the result

When trying to create a post, inside learning MFE, the Discussion/Question border highlight doesn't change on click.

Tested on Quince.2
Tutor 17.0.2

The tabs course menu does not display the "more" button for responsive support during the first load, creating a horizontal scroll. I have to resize the screen to make it work.

frontend-platform supports runtime configuration since 2.5.0 (see the PR that introduced it), but it requires MFE cooperation. We should avoid making configuration values constant, in order to make it possible to change them after initialization.

Failure on stage

The change was first merged to master in 9f84230, but it was reported to introduce an issue as described in #382. The change was reverted by 67b0b33.

We need to either try and reproduce the issue to gather more data, or try to find out what's wrong by analyzing the code.

PRs

• #379 (merged)
• #382 (revert)
• #386 (second attempt)

Steps to Reproduce

1- Maker a course start date on 3 June 2024
2- Set the "Days early for beta users" to 5
3- Add the user as beta tester
4- Navigate to openedx using beta tester
5- Observe that the Discussion forum is displayed and the beta tester can add posts

Original issue: openedx/wg-build-test-release#372

Hi. I'm running openedx palm 3 with tutor. When switching the discussions MFE to the master branch, after launch, I get this page:

The said line is const { params: { page } } = useRouteMatch(`${Routes.COMMENTS.PAGE}?`);. So I assume that the useRouteMatch function is returning null. Can you please help me with this?

This issue was first posted in the forum.

Issue

When we use this MFE on Tutor, I haven't had the opportunity to test it on devstack, the favicon and siteName in the title do not render. Similarly, the title is not translated into the current language, it always shows in English as is defined in the index.html file:

Possible Reason

This is likely due to this MFE trying to access the favicon directly in the assets folder as it is being done here:

In the other MFEs, they use the react-helmet package to override the head tag, similar to how it is being done in the profile MFE here.

How to reproduce

1. Install any version of tutor
2. Create a superuser using the command: tutor local do createuser --staff --superuser yourusername [email protected]
3. Sign in to tutor with the created user
4. Import the demo course using the command: tutor local do importdemocourse
5. Visit the discussions page for the demo course at this url
6. The favicon and the sitename will not render.

Or you can just visit the sandbox environment, which is running Tutor version 17.0.0. You can visit it at this link

The user has the opportunity to vote for his post:

But if you look at how it worked for Discussion XBlock, you can see that the ability to vote for your post is blocked and the button is not active for the user:

I found in the documentation that the user should not be able to vote for his post Discussions Docs

I found out that this resolution is obtained on the backend. But this is not used to Discussion MFE.

It might be worth paying attention to this.

Abstract
Node 16's support will end on September 11, 2023. So we have to upgrade node JS to v18 before that.

Extras
Project should use .nvmrc to have a consistent node version
We have to update Readme accordingly.

Upgrade Node JS from 16 to 18

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Datasource	Name	Replacement PR?
npm	babel-plugin-react-intl

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• fix(deps): update dependency @edx/frontend-component-header to v5.3.4
• fix(deps): update dependency @openedx/frontend-slot-footer to v1.0.3
• fix(deps): update dependency @edx/frontend-platform to v8.1.1
• fix(deps): update dependency @openedx/paragon to v22.7.0
• fix(deps): update dependency dompurify to v2.5.6
• chore(deps): update dependency axios to v1
• chore(deps): update dependency axios-mock-adapter to v2
• chore(deps): update dependency eslint-plugin-simple-import-sort to v12
• chore(deps): update dependency glob to v11
• chore(deps): update dependency husky to v9
• chore(deps): update dependency node to v20
• chore(deps): update testing-library monorepo (major) (@testing-library/jest-dom, @testing-library/react, @testing-library/user-event)
• fix(deps): update dependency @reduxjs/toolkit to v2
• fix(deps): update dependency @tinymce/tinymce-react to v5
• fix(deps): update dependency dompurify to v3
• fix(deps): update dependency react-redux to v9
• fix(deps): update dependency redux to v5
• fix(deps): update dependency tinymce to v7
• fix(deps): update dependency yup to v1
• fix(deps): update react monorepo to v18 (major) (react, react-dom)
• 🔐 Create all rate-limited PRs at once 🔐

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update dependency @openedx/frontend-build to v14.0.15
• chore(deps): update dependency axios to v0.28.1
• chore(deps): update dependency glob to v7.2.3
• fix(deps): update dependency @edx/openedx-atlas to v0.6.1
• fix(deps): update dependency formik to v2.4.6
• fix(deps): update dependency tinymce to v5.10.9
• fix(deps): update dependency @tinymce/tinymce-react to v3.14.0
• fix(deps): update dependency core-js to v3.38.0
• fix(deps): update react-router monorepo to v6.26.0 (react-router, react-router-dom)
• chore(deps): update dependency @edx/reactifex to v2
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

There is a problem in the left vertical list of the posts titles with the preview of the post body: The post body is not decoded correctly if it's written in a non-latin alphabet (For the Greek language in my case), as it is shown on my screenshot here.

The solution I have found and tested is quite simple though.

In the file frontend-app-discussions/src/discussions/posts/post/PostLink.jsx
at the beginning you have to import 'he':

import he from 'he';

and at the following line:

you have to decode the previewBody like so:

{isPostPreviewAvailable(previewBody) ? he.decode(previewBody) : intl.formatMessage(messages.postWithoutPreview)}

And that fixes the problem.

That's my solution but I guess there are other ways to deal with it as well...

Expected behavior

Clicking your browser's "back" button from the Discussion tab should take you to the previous page.

Steps to reproduce

1. Start on any course page, such as https://apps.redwood.demo.edly.io/learning/course/course-v1:HinaX+HX101+2024_T2/home
2. Click on "Discussion".
3. Use your browser's back button.
4. Witness a brief moment of "All posts sorted by recent activity" on the left.

The URL changes briefly from
https://apps.redwood.demo.edly.io/discussions/course-v1:HinaX+HX101+2024_T2/posts
to
https://apps.redwood.demo.edly.io/discussions/course-v1:HinaX+HX101+2024_T2/
and then back to
https://apps.redwood.demo.edly.io/discussions/course-v1:HinaX+HX101+2024_T2/posts

The original issue was reported on the BTR board as part of the redwood testing effort: openedx/wg-build-test-release#346

Description

See the parent ticket for the general description and motivation, openedx/public-engineering#267. Make sure to follow its recommendations for each step of the process.

This repo is currently using React JS v16. We need to upgrade it to React 17 before moving to latest React version(v18).
React 17 doesn’t add any new developer-facing features, so its upgrade might not cause any breaking changes. Our end goal is to upgrade React to v18 but v18 no longer support enzyme, so we are upgrading to React 17 and then we’ll migrate from enzyme.

Epic Link

React 17 upgrade