2018-03-08 Meeting Notes
Date
Goals
Time | Item | Who | Notes |
---|---|---|---|
10 min | Status | Everyone | |
3.7 minutes | Paragon Modal/ Paragon 3 | Turc | https://github.com/edx/paragon/pull/153 |
Versioning, breaking changes, integration testing | |||
Theming | |||
45 seconds | GraphQL | Jae | |
30 seconds | Unmeeting - VoiceOver tutorial | Farhanah |
Notes
New Relic Browser vs Speedcurve
- Do we use it?
- NO
- What about errors?
- Need something that does this better
- Does Speedcurve have SPA capabilities?
- Let's check this out
Integration Testing for Paragon/other frontend libraries
- npm prepare
- npm install (just to install deps) runs the production build
- no longer need to check dist into github
- let's add to Paragon
- Should consumers track Paragon changes?
- yes
- Good to get notice of (major) changes before they're merged
- We should probably announce changes broadly (release announcements email?)
- But we shouldn't slow down releases?
- Communicate early and often
- Breaking change: expected outcome is different
Unmeeting
- It is still happening! Everyone should come
- Learn to use VO:
- Screenreader study group
- Everyone should attend!!
- Regression prevention
- we need tooling
- axe core
- react axe https://github.com/dequelabs/react-axe
- google lighthouse
- need to think strategically about this
GraphQL
- Redux: state management layer
- GraphQL: spec for ways to access data
- frontend has a ton of control over what the backend sends
- specify exactly hte data you need from sources
- GraphQL doesn't need to affect the entire application
- cookiecutter: can work with REST or GraphQL
- Lets keep it in with some clear warnings