Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

\uD83D\uDDD3 Date

\uD83D\uDC65 Participants

\uD83E\uDD45 Goals

\uD83D\uDDE3 Discussion topics

Time

Item

Presenter

Notes

5-10 min

Form.Autosuggest props ?'s

Max Frank

  • https://paragon-openedx.netlify.app/components/form/form-autosuggest/

    • onSelected vs onChange

      • I noticed that onSelected will fire during any onChange event

      • Can the component have both of these attributes?

    • In the example:

      • (value) => setSelected(prevState => ({ selected: { ...prevState.selected, title: value } }))

      • Why not just setSelected('new-string-value'), instead of the object?

    • Form.AutosuggestOption doesn’t seem to be receiving the key prop — receiving error when I run tests

2 min

[inform] Storybook docs for Paragon v2

Adam Stankiewicz

Context: edx-platform is still using v2.6.4 and will remain at this version for an indeterminate amount of time. Given that we are still working out of edx-platform and yet didn’t have a clear way of knowing what was available and what wasn’t.

Solution: https://paragon-openedx-v2.netlify.app/

3-5 mins

[inform] Collecting data on users' color scheme preference via @edx/frontend-platform

Adam Stankiewicz

Context: As we’re working towards being able to support runtime theming for Open edX, one of the longer term goals is that we’d be able to support a true light vs. dark mode in the platform.

Users can set system preferences to use light vs. dark mode and this is reflected via the prefers-color-scheme media query.

Solution: We’d like to start collecting data on what percentage of users have their system preferences set to prefer a dark mode.

  • Dispatch a new Segment event from AppProvider used by all MFEs via useTrackColorSchemeChoice (source).

  • Handles

✅ Action items

  •  

⤴ Decisions

  • No labels