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 5 Current »

\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

Notes:

  • A11y check with Jeff Witt (Deactivated) when skill builder autosuggest is ready

  • Brian Smith raised https://github.com/openedx/paragon/issues/1732 cleanup that could be done simultaneously

  • Adam Stankiewicz feels like should be distinct things

  • Need full clarity if autosuggest supports freeform text or not

  • Gabriel Weinberg to raise design issues with multiselect and form autosuggest.

    • how to handle form autosuggest error text and freeform text

    • Revisit multiselect issue and get update on status and whats needed

  • Max Frank Suggest creating the github issue and including the error issue as well

    • bug and engineering labels

2 min

[inform] Storybook docs for Paragon v2

Adam Stankiewicz Jason Wesson

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/

Gabriel Weinberg add direct link to confluence documentation

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 and source).

  • Included in v3.4.1 of @edx/frontend-platform.

Notes:

  • Jeff Witt (Deactivated) In terms of UI, one should be able to say i prefer dark mode, and the browser should recognize it and set it for you. Yes No and Default settings corresponding between browser and system.

2 mins

developer role type and official design tokens support in Figma is on their roadmap

Interesting 🤔 Lots of new cool things coming in the pipeline that might be relevant for us.

Merge updates

Adam Stankiewicz

Radio and Checkbox errors with color updates will be merged

Request for PR review

Adam Stankiewicz

RG has a Draft PR for the design tokens project Brian Smith can you please take a look? Muchas gracias

Hackathon!

Jeff Witt (Deactivated)

Consider dark mode project for hackathons to carve out dedicated time.

Hackathon might also be a good way to chip away at other Paragon backlog items, just saying

tech debt question

Jeff Witt (Deactivated)

Is there any progress on edx-platform and studio to upgrade to the most modern paragon?

✅ Action items

  •  

⤴ Decisions

  • No labels