[BD-46] feat: implement i18n in Paragon components and in docs site #1100

viktorrusakov · 2022-02-18T09:24:49Z

This is an ongoing work to implement i18n support in Paragon.

To see i18n in action go to https://deploy-preview-1100--paragon-openedx.netlify.app/components/alert/?feature=LANGUAGE_SWITCHER, switch language in settings menu and see how the label of 'Dismiss' button of the Alert changes (there are sample translation for this label in this PR).

JIRA:

netlify · 2022-02-18T09:24:55Z

✅ Deploy Preview for paragon-openedx ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	`18760fd`
🔍 Latest deploy log	https://app.netlify.com/sites/paragon-openedx/deploys/62ab184f94329c000951cb0a
😎 Deploy Preview	https://deploy-preview-1100--paragon-openedx.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

netlify · 2022-02-18T09:24:55Z

✔️ Deploy Preview for paragon-edx ready!

🔨 Explore the source changes: 08ebdef

🔍 Inspect the deploy log: https://app.netlify.com/sites/paragon-edx/deploys/623058c031fb4e00087735a5

😎 Browse the preview: https://deploy-preview-1100--paragon-edx.netlify.app

openedx-webhooks · 2022-02-18T09:24:56Z

Thanks for the pull request, @viktorrusakov!

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

adamstankiewicz · 2022-02-28T23:05:23Z

src/Card/index.jsx

@@ -24,7 +24,7 @@ const Card = React.forwardRef(({
        clickable: isClickable,
      })}
      ref={ref}
-      tabindex={isClickable ? '0' : '-1'}


[inform] This was fixed in a separate PR and should be all set upon a rebase of this branch.

Yeah, rebasing removed it, thanks!

adamstankiewicz · 2022-02-28T23:08:42Z

src/DataTable/DataTableLayout.jsx

 };

 DataTableLayout.propTypes = {
  className: PropTypes.string,
  children: PropTypes.node.isRequired,
+  filtersTitle: PropTypes.string,


This prop should likely accept things beyond strings (either node or element maybe?) , e.g. say a consumer wants to wrap the title in a custom element with a class name, (e.g., filtersTitle={<span className="...">{...}</span>}).

Yeah, it definitely should, missed it, thanks

adamstankiewicz · 2022-02-28T23:12:02Z

src/DataTable/FilterStatus.jsx

+        {clearFiltersText || (
+          <FormattedMessage
+            id="pgn.DataTable.FilterStatus.clearFiltersText"
+            defaultMessage="Clear Filters"


Lowercase "filters"

Updated, thanks

adamstankiewicz · 2022-02-28T23:14:35Z

src/DataTable/ExpandAll.jsx

@@ -1,12 +1,29 @@
 import React from 'react';
 import PropTypes from 'prop-types';
+import { FormattedMessage } from 'react-intl';
 import { Button } from '..';

 const ExpandAll = ({ getToggleAllRowsExpandedProps, isAllRowsExpanded }) => (
  <span {...getToggleAllRowsExpandedProps()}>
    {isAllRowsExpanded


formatting nit:

{isAllRowsExpanded ? ( <Button variant="link" size="inline"> <FormattedMessage id="pgn.DataTable.ExpandAll.collapseAllLabel" defaultMessage="Collapse all" description="Title of the filters components" /> </Button> ) : ( <Button variant="link" size="inline"> <FormattedMessage id="pgn.DataTable.ExpandAll.expandAllLabel" defaultMessage="Expand all" description="Title of the filters components" /> </Button> )}

yeah, this looks better, thanks 🙂

adamstankiewicz · 2022-02-28T23:18:10Z

src/DataTable/selection/ControlledSelectionStatus.jsx

  className: PropTypes.string,
+  /** A text that appears on the `Clear selection` button, defaults to 'Clear Selection' */
  clearSelectionText: PropTypes.string,


Should this also handle elements in addition to strings as well?

it should, thanks, updated

adamstankiewicz · 2022-02-28T23:25:03Z

www/src/components/Settings.jsx

              floatingLabel="Direction"
            >
              <option value="ltr">Left to right</option>
              <option value="rtl">Right to left</option>
            </Form.Control>
          </Form.Group>
        )}
+        {FEATURES.LANGUAGE_SWITCHER && (


Let's maybe use Stack here to add a bit of vertical space between these 3 Form.Control components (e.g., <Stack gap={5}>) ?

Good idea! Added Stack gap={3}, setting gap to 5 seemed like too much extra space

adamstankiewicz · 2022-02-28T23:27:03Z

www/src/context/SettingsContext.jsx

+      document.body.setAttribute('dir', value);
+    }
+    setSettings(prevState => ({ ...prevState, [key]: value }));
+    global.localStorage.setItem('pgn__settings', JSON.stringify({ ...settings, [key]: value }));


Nice, this is a great idea to colocate the settings to a single storage item!

codecov · 2022-03-15T09:21:00Z

Codecov Report

Merging #1100 (18760fd) into master (0765840) will increase coverage by 0.00%.
The diff coverage is 93.10%.

@@           Coverage Diff           @@
##           master    #1100   +/-   ##
=======================================
  Coverage   90.87%   90.87%           
=======================================
  Files         198      199    +1     
  Lines        3266     3288   +22     
  Branches      735      753   +18     
=======================================
+ Hits         2968     2988   +20     
- Misses        284      286    +2     
  Partials       14       14

Impacted Files	Coverage Δ
src/DataTable/DataTableLayout.jsx	`87.50% <ø> (ø)`
.../DataTable/selection/ControlledSelectionStatus.jsx	`100.00% <ø> (ø)`
src/DataTable/selection/SelectionStatus.jsx	`100.00% <ø> (ø)`
src/DataTable/SidebarFilters.jsx	`25.00% <60.00%> (+12.50%)`	⬆️
src/Alert/index.jsx	`97.36% <100.00%> (+0.14%)`	⬆️
src/DataTable/ExpandAll.jsx	`100.00% <100.00%> (ø)`
src/DataTable/FilterStatus.jsx	`100.00% <100.00%> (ø)`
src/DataTable/RowStatus.jsx	`100.00% <100.00%> (ø)`
src/DataTable/selection/BaseSelectionStatus.jsx	`100.00% <100.00%> (ø)`
src/Toast/index.jsx	`75.00% <100.00%> (+3.57%)`	⬆️
... and 1 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 86d19c1...18760fd. Read the comment docs.

viktorrusakov · 2022-03-22T17:10:44Z

.tx/config

+[main]
+host = https://www.transifex.com
+
+[edx-platform.paragon]


Should this be a separate project, not edx-platform?

As discussed, we will keep this under edx-platform for the time being, as it seems most of the projects that consume Paragon are under this project as well. I agree it's a bit odd, though.

adamstankiewicz

Awesome! Left a few nits here and there, but this is looking great 🎉

adamstankiewicz · 2022-03-27T17:28:16Z

.tx/config

+[main]
+host = https://www.transifex.com
+
+[edx-platform.paragon]


As discussed, we will keep this under edx-platform for the time being, as it seems most of the projects that consume Paragon are under this project as well. I agree it's a bit odd, though.

adamstankiewicz · 2022-03-27T17:28:24Z

.tx/config

+file_filter = src/i18n/messages/<lang>.json
+source_file = src/i18n/transifex_input.json
+source_lang = en
+type = STRUCTURED_JSON


nit: newline

adamstankiewicz · 2022-03-27T17:31:33Z

Makefile

+i18n = ./src/i18n
+transifex_input = $(i18n)/transifex_input.json
+
+NPM_TESTS=build i18n_extract lint test is-es5


I think the is-es5 script can be removed, as Paragon does not have it defined?

true, thanks!

adamstankiewicz · 2022-03-27T17:31:52Z

Makefile

+# This target is used by Travis.
+validate-no-uncommitted-package-lock-changes:
+	# Checking for package-lock.json changes...
+	git diff --exit-code package-lock.json


nit: newline

adamstankiewicz · 2022-03-27T17:34:09Z

README.md

+  )
+```
+
+Note that if you are using ``frontend-platform``'s ``AppProvider`` component you don't need a separate context,


nit: @edx/frontend-platform

adamstankiewicz · 2022-03-27T17:37:01Z

docs/decisions/0015-i18n-support.rst

@@ -56,10 +56,10 @@ Consequences
    ReactDOM.render(
      <AppProvider>
        <App />
-      </IntlProvider>,
+      </AppProvider>,


adamstankiewicz · 2022-03-27T17:37:48Z

package.json

@@ -47,6 +48,7 @@
    "prop-types": "^15.8.1",
    "react-bootstrap": "^1.6.4",
    "react-focus-on": "^3.5.4",
+    "react-intl": "2.9.0",


Thanks for keeping this pinned 🙌

adamstankiewicz · 2022-03-27T17:47:12Z

src/DataTable/tests/FilterStatus.test.jsx

-  it('hides filter text', () => {
-    const wrapper = mount(<FilterStatusWrapper value={instance} props={filterPropsNoFiltered} />);
-    expect(wrapper.text()).toEqual('');
-  });


Should we be removing this test? Is there another test covering the showFilteredFields={false} case? There is at least one or two teams using this prop to hide the "Filtered by..." text because it shows the accessor's value which may be a programmatic value, e.g. "Filtered by requestStatus".

Yeah, my bad...fixed it and reverted the change, glad you noticed, thanks!

adamstankiewicz · 2022-03-27T17:53:06Z

www/src/components/PropsTable.jsx

@@ -69,7 +69,7 @@ const PropsTable = ({ props: componentProps, displayName, content }) => (
    {content && <div className="small mb-3">{content}</div>}
    {componentProps.length > 0 ? (
      <ul className="list-unstyled">
-        {componentProps.map(metadata => <Prop key={metadata.name} {...metadata} />)}
+        {componentProps.map(metadata => metadata.name !== 'intl' && <Prop key={metadata.name} {...metadata} />)}


nit: think it's worth creating a IGNORED_COMPONENT_PROPS=['intl'] (or similar) and use it in a .filter(...) to make this simple to add to in the future if needed?

This definitely seems like a better approach, thanks 🙂

adamstankiewicz · 2022-03-28T21:52:00Z

@viktorrusakov Is there any way we'd be able to support a case where a code repository is using @edx/paragon (with i18n) and does not use @edx/frontend-platform, but already has react-intl@5 installed? Will this reliance on the older react-intl@2 in Paragon cause issue in this case?

Related: One idea worth exploring here is whether we prioritize getting react-intl upgraded in frontend-platform to v5 instead of v2, so that we don't have these version conflicts. There is an issue about this on the Frontend Working Group board. I'd be curious to hear your thoughts on this as well 😄

viktorrusakov · 2022-04-01T06:38:31Z

@adamstankiewicz I'm pretty positive that there will be issues if provider has react-intl@5. I believe the context component provided by react-intl@5 is not compatible with react-intl@2, so Paragon's components will not be able to receive required translations this way. I might be wrong though, I can test it to be sure.

As for updating react-intl in frontend-platform I do believe that's the best approach, as the issue you linked stated we are falling quite a bit behind, since there has already been 3 major releases (from react-intl@2 to react-intl@5). I don't know how much work it would take though...
Also, if we do this it would be a good opportunity to also update Transifex scripts and remove deprecated packages from usage😉

adamstankiewicz · 2022-04-01T11:39:06Z

@viktorrusakov Yeah, it might be worth a manual test, if possible. I'm also leaning towards prioritizing the upgrade to react-intl@5 in @edx/frontend-platform regardless as an enabler for this i18n change in Paragon.

I just added some notes to the linked issue about the impacts of each breaking change in react-intl since v2. It doesn't seem like it would be too bad of a migration for @edx/frontend-platform or consumers, and we'll have to do it regardless one of these days 😅

Let me know your thoughts after you give those release notes a review! Maybe we can chat about this in more detail during our "in-person" sync today.

adamstankiewicz · 2022-04-01T11:47:56Z

Also, if we do this it would be a good opportunity to also update Transifex scripts and remove deprecated packages from usage😉

@viktorrusakov Yes, I agree we should do something here as well. I'm not sure if we will directly get involved with upgrading Transifex scripts in each project, though we could likely go that route, if we'd like. I might be leaning more towards creating the documentation / examples for it, and empowering teams to make the improvements themselves. Open to your thoughts here on methodology, too, of course 😄

viktorrusakov · 2022-04-08T07:25:48Z

@adamstankiewicz Tested Paragon's i18n implementation with react-intl@5 in consuming application, unfortunately it does't work😞, Paragon just doesn't recognize IntlProvider component from future releases (I've also tested it withreact-intl@3 - same problem), here's the error I get
[React Intl] Could not find required `intl` object. <IntlProvider> needs to exist in the component ancestry. Using default message as fallback.
Once I downgrade to react-intl@2 this goes away and i18n works just fine in consuming app.

Judging from the breaking changes list for v3 release I think the reason might be

IntlProvider no longer inherits from upstream IntlProvider

I don't know what this changes exactly 😅 but IntlProvider might have been changed incompatibly with previous releases, that's my guess. Also, they are saying that in v3 they started using new React Context API, this might also be one of the reasons.

adamstankiewicz

Hey @viktorrusakov, I left a few comments throughout the PR. Two notable concerns:

Should we treat react-intl as a peer dependency (see comment for more details)?
If the default message is from a variable defined as a constant (as in Alert), it doesn't appear that its string is exported in the exported transifex_input.json file, e.g.:

{
  "pgn.Alert.closeLabel": {
    "developer_comment": "Label of a close button on Alert component"
  },
}

On another note, I'm working to get the PRs for the Transifex pipeline job created for the repo in our Jenkins instance as well along with alerting for when the jobs fail.

adamstankiewicz · 2022-06-10T03:46:39Z

package.json

@@ -55,6 +56,7 @@
    "prop-types": "^15.8.1",
    "react-bootstrap": "^1.6.4",
    "react-focus-on": "^3.5.4",
+    "react-intl": "^5.25.0",


Should we treat react-intl as a peer dependency, especially since it's already included as a dependency in @edx/frontend-platform? That way, @edx/frontend-platform's version of react-intl would remain the source of truth. It would also allow peer dependency warnings during install if the consumer doesn't have react-intl (at the correct version) in their installed dependency tree.

Agree, that's a great idea!

adamstankiewicz · 2022-06-10T03:48:35Z

src/DataTable/ExpandAll.jsx

+        <FormattedMessage
+          id="pgn.DataTable.ExpandAll.expandAllLabel"
+          defaultMessage="Expand all"
+          description="Title of the filters components"


Should this description differ from the "Collapse all" message above?

Yeah... and "Collapse all" message also should be different and not copied from some filters component 😅
updated, thanks!

adamstankiewicz · 2022-06-10T03:50:14Z

src/DataTable/FilterStatus.jsx

@@ -23,7 +24,15 @@ const FilterStatus = ({
        size={size}
        onClick={() => setAllFilters([])}
      >
-        {clearFiltersText}
+        {clearFiltersText === undefined


[curious] Why the explicit check for the undefined type versus relying on a falsey value alone? For example, if consumer passes an empty string, I'd think we might still want to fallback to the default message?

Good question! Initially I tried to check for falsey value but decided against it because there is a specific test case which tests that no text gets rendered if you pass an empty string, it was failing.

I could change that test but I thought that maybe there is a use case for not displaying any text..

Hmm, interesting. I suppose that could be possible; best to handle it explicitly I guess, considering there is a specific test for it 🤷‍♂️ Though, I cant imagine why you'd want to do this haha.

adamstankiewicz · 2022-06-10T03:53:31Z

src/DataTable/selection/BaseSelectionStatus.jsx

+            <FormattedMessage
+              id="pgn.DataTable.BaseSelectionStatus.selectAllText"
+              defaultMessage="Select all {itemCount}"
+              description="Clear selection button label"


Should this description reflect that it's the "Select all" message?

Definitely, thanks!

adamstankiewicz · 2022-06-10T03:55:00Z

src/Toast/index.jsx

  const [autoHide, setAutoHide] = useState(true);
+  const intlCloseLabel = closeLabel || intl.formatMessage({
+    id: 'pgn.Toast.closeLabel',
+    defaultMessage: 'Close',


Should this be using the TOAST_CLOSE_LABEL_TEXT constant?

Maybe not, if the string isn't getting extracted when this is treated as a constant 🙃

adamstankiewicz · 2022-06-10T03:58:49Z

www/src/components/Settings.jsx

        <Form.Group>
          <Form.Control
            as="select"
-            value={currentTheme}
-            onChange={onThemeChange}
+            value={settings.theme}


Should the Form.Control for the direction switcher also be reading from settings?

Yeah, good catch, thanks! Rebasing is hard 🙃

adamstankiewicz

LGTM 🚀 I have a PR created that is also awaiting review from our DevOps team to enable the Transifex pipeline jobs on Jenkins to automate the push/pull of translations for the repo.

adamstankiewicz · 2022-06-17T10:38:35Z

src/DataTable/FilterStatus.jsx

@@ -23,7 +24,15 @@ const FilterStatus = ({
        size={size}
        onClick={() => setAllFilters([])}
      >
-        {clearFiltersText}
+        {clearFiltersText === undefined


Hmm, interesting. I suppose that could be possible; best to handle it explicitly I guess, considering there is a specific test for it 🤷‍♂️ Though, I cant imagine why you'd want to do this haha.

openedx-webhooks · 2022-06-17T11:00:05Z

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

# [20.0.0](v19.25.3...v20.0.0) (2022-06-17) * feat!: implement i18n in Paragon components and in docs site (#1100) ([53e0ac6](53e0ac6)), closes [#1100](#1100) ### BREAKING CHANGES * By adding i18n support to the Paragon design system, we are introducing a peer dependency on `[email protected]` or greater. This may be a breaking change for some consumers, if your repository: * Uses v1 of `@edx/frontend-platform` * Uses older version of `react-intl` than v5.25.0 directly. * Does not use `react-intl`.

edx-semantic-release · 2022-06-17T11:11:13Z

🎉 This PR is included in version 20.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

openedx-webhooks added blended PR is managed through 2U's blended developmnt program needs triage labels Feb 18, 2022

viktorrusakov marked this pull request as draft February 18, 2022 09:46

adamstankiewicz reviewed Feb 28, 2022

View reviewed changes

viktorrusakov force-pushed the vrusakov/implement-i18n branch 3 times, most recently from ba82c89 to 08ebdef Compare March 15, 2022 09:13

viktorrusakov force-pushed the vrusakov/implement-i18n branch from 08ebdef to 61e880b Compare March 22, 2022 16:48

viktorrusakov marked this pull request as ready for review March 22, 2022 16:53

viktorrusakov changed the title ~~[BD-46] feat: implement i18n in Paragon component and in docs site~~ [BD-46] feat: implement i18n in Paragon components and in docs site Mar 22, 2022

viktorrusakov commented Mar 22, 2022

View reviewed changes

viktorrusakov force-pushed the vrusakov/implement-i18n branch from bf1ef73 to f14c771 Compare March 25, 2022 12:36

adamstankiewicz reviewed Mar 27, 2022

View reviewed changes

viktorrusakov force-pushed the vrusakov/implement-i18n branch from f14c771 to c607100 Compare April 1, 2022 06:05

adamstankiewicz mentioned this pull request Apr 1, 2022

Frontend Working Group Meeting 2022-04-07 openedx/wg-frontend#93

Closed

viktorrusakov force-pushed the vrusakov/implement-i18n branch from c607100 to acc532e Compare April 8, 2022 07:29

arbrandes mentioned this pull request Apr 8, 2022

Frontend Working Group Meeting 2022-04-21 openedx/wg-frontend#97

Closed

viktorrusakov force-pushed the vrusakov/implement-i18n branch 2 times, most recently from 6b1734e to 02d3268 Compare May 11, 2022 08:20

adamstankiewicz mentioned this pull request May 13, 2022

Raccoon Gang (5/13) #1285

Closed

27 tasks

natabene assigned adamstankiewicz May 14, 2022

natabene unassigned adamstankiewicz May 16, 2022

adamstankiewicz mentioned this pull request May 20, 2022

Raccoon Gang (5/20) #1289

Closed

17 tasks

adamstankiewicz linked an issue May 20, 2022 that may be closed by this pull request

i18n support for Paragon components #1298

Closed

viktorrusakov force-pushed the vrusakov/implement-i18n branch 3 times, most recently from c259dce to cd58bdb Compare June 3, 2022 08:10

adamstankiewicz reviewed Jun 10, 2022

View reviewed changes

viktorrusakov added 9 commits June 15, 2022 23:26

feat: add i18n to docs site and to DataTable component

0d29c25

chore: update snapshots and fix proptypes

b766533

build: add transifex scripts

cf57936

docs: update readme with i18n information

89a1be3

chore: small miscellaneous fixes / improvements

1def286

chore: remove test translations

2924e11

feat: upgrade to react-intl@5

1d4ea68

test: add IntlProvider wrapper to tests which include i18n components

a15a66c

chore: cleanup after rebase

6db5cf2

viktorrusakov force-pushed the vrusakov/implement-i18n branch from cd58bdb to fb7519d Compare June 16, 2022 07:57

openedx-webhooks removed the needs triage label Jun 16, 2022

chore: move react-intl to peer dependencies and fix direction switcher

18760fd

viktorrusakov force-pushed the vrusakov/implement-i18n branch from fb7519d to 18760fd Compare June 16, 2022 11:47

adamstankiewicz approved these changes Jun 17, 2022

View reviewed changes

adamstankiewicz merged commit 53e0ac6 into openedx:master Jun 17, 2022

edx-semantic-release added the released label Jun 17, 2022

[BD-46] feat: implement i18n in Paragon components and in docs site #1100

[BD-46] feat: implement i18n in Paragon components and in docs site #1100

Conversation

viktorrusakov commented Feb 18, 2022 • edited by adamstankiewicz Loading

netlify bot commented Feb 18, 2022 • edited Loading

✅ Deploy Preview for paragon-openedx ready!

netlify bot commented Feb 18, 2022 • edited Loading

openedx-webhooks commented Feb 18, 2022 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

viktorrusakov Mar 15, 2022 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

codecov bot commented Mar 15, 2022 • edited Loading

Codecov Report

Choose a reason for hiding this comment

Choose a reason for hiding this comment

adamstankiewicz left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

viktorrusakov Apr 1, 2022 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

adamstankiewicz commented Mar 28, 2022

viktorrusakov commented Apr 1, 2022

adamstankiewicz commented Apr 1, 2022

adamstankiewicz commented Apr 1, 2022

viktorrusakov commented Apr 8, 2022

adamstankiewicz left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

adamstankiewicz left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

openedx-webhooks commented Jun 17, 2022

edx-semantic-release commented Jun 17, 2022

viktorrusakov commented Feb 18, 2022 •

edited by adamstankiewicz

Loading

netlify bot commented Feb 18, 2022 •

edited

Loading

netlify bot commented Feb 18, 2022 •

edited

Loading

openedx-webhooks commented Feb 18, 2022 •

edited

Loading

viktorrusakov Mar 15, 2022 •

edited

Loading

codecov bot commented Mar 15, 2022 •

edited

Loading

viktorrusakov Apr 1, 2022 •

edited

Loading