Base Web, Uber’s New Design System for Building Websites in React

Post by gramstrong » Fri, Apr 26, 2019, 6:22 PM UTC

revskill wrote: post #10

I'm surprised that many huge React libraries don't expose its core Context for user to consume. Context is the most important concept in React. Actually, a library just need users to provide the right types of Context to be flexible. I'm tired of the "lock in" API, in which, it doesn't allow me to just get my context data into its arguments API. In this sense, you can consider Context as the local version of Redux.

Post by sbr464 » Fri, Apr 26, 2019, 6:30 PM UTC

d357r0y3r wrote: post #5

Imagine creating this beast of a "framework" and not even using TypeScript or Flow. What are you thinking? Edit: It does use Flow.

Post by revskill » Fri, Apr 26, 2019, 6:34 PM UTC

gramstrong wrote: post #21

revskill wrote: post #10

I'm surprised that many huge React libraries don't expose its core Context for user to consume. Context is the most important concept in React. Actually, a library just need users to provide the right types of Context to be flexible. I'm tired of the "lock in" API, in which, it doesn't allow me to just get my context data into its arguments API. In this sense, you can consider Context as the local version of Redux.

As someone who stopped doing React development before Context became a "thing", is it possible to ELI5 in a couple sentences why it is such an important concept?

Post by sbr464 » Fri, Apr 26, 2019, 6:37 PM UTC

sbr464 wrote: post #23

d357r0y3r wrote: post #5

Imagine creating this beast of a "framework" and not even using TypeScript or Flow. What are you thinking? Edit: It does use Flow.

My only issue is TS usage with extremely large/complex components/containers. For example, files around 500 lines of code, I've temporarily removed TS, done a few other optimizations (ternaries for obvious If/Else statements, etc) to reduce to ~200-230 lines total. The file is instantly easier to reason about and modify. I wish there was a plugin that just did this automatically so you could toggle it back on when do…

  togglePanel = (newTogglePanelComponentState: Boolean) => {
    return this.setState({ panelToggleState: newTogglePanelComponentState });
  }

  togglePanel = bool => this.setState({ panelToggle: bool })

Post by revskill » Fri, Apr 26, 2019, 6:41 PM UTC

miksuv wrote: post #28

revskill wrote: post #10

I'm surprised that many huge React libraries don't expose its core Context for user to consume. Context is the most important concept in React. Actually, a library just need users to provide the right types of Context to be flexible. I'm tired of the "lock in" API, in which, it doesn't allow me to just get my context data into its arguments API. In this sense, you can consider Context as the local version of Redux.

Are you talking about the theme? Can you be more specific?