View Source

Date

12 Apr 2018

Time	Item	Who	Notes
10 min	Status	Everyone
10 min	Internationalization in React, as seen in studio-frontend	Eric	Initial draft, suggestions welcome!
1 min	New Relic Browser	Dave	To kill or not to kill?
10 min	Microgrooming	Ari	Followup on our suggestion to review FedX issues that have come up recently. We'll see how it goes this week and determine whether we want to continue!
	Arch squad status	Ari/Dave	Some deets on the upcoming work we're planning including a GraphQL Spike.

We should definitely not use it
Existing modal was pretty heavily integrated with the rest of the page
Already built, we were just changing stuff inside it
~~For legacy components, leave as is, new stuff use Paragon~~
Convert where possible!!!
For legacy backbone stuff event emitters can be a good solution
- Also Ari has a PR she still needs to land...
Modal experiences are already inconsistent

https://github.com/edx/studio-frontend/pull/180
Uses https://github.com/yahoo/react-intl
Can we chat with about this and maybe pull it into the i18n minute?
- Yes!
You can nest languages!
You can do cool stuff with a11y requirements/aria labels etc.
- WrappedMessage wraps every formatted message in a span specifying lang
- WCAG2AA compliance!!
Reactifex – our way of working around Transifex's JSON formatting limitations
What about future decoupled frontends?
- Recommend something like this for future decoupled frontends
- However maybe it should all live in one place
- Let's add it to the cookiecutter!

Does anybody use it?
- 2.5 developers
- ecommerce, mktg, platform use it for overall performance issues
- error catching is useful
Is Speedcurve better?
- What about SPAs? NR Browser does a good job with this.
It is really expensive.