ryanflorence

animated.DialogOverlay = animated(DialogOverlay)
animated.DialogContent = animated(DialogContent)

function NewPostDialog({ date, show, onDismiss }) {
  const rootRef = useRef(null)

  const transitions = useTransition(show, null, {
    from: { opacity: 0, y: -10, blur: 0 },
    enter: { opacity: 1, y: 0, blur: 8 },
    leave: { opacity: 0, y: -10, blur: 0 },

astoilkov

Async Operations with useReducer Hook

9 March, 2019

We were discussing with @erusev what we can do with async operation when using useReducer() in our application. Our app is simple and we don't want to use a state management library. All our requirements are satisfied with using one root useReducer(). The problem we are facing and don't know how to solve is async operations.

In a discussion with Dan Abramov he recommends Solution 3 but points out that things are fresh with hooks and there could be better ways of handling the problem.

Problem

jonoirwinrsa

Description: >
  Script to create a SSL certificate, S3 bucket and Cloudfront distribution.

###############################################################################
Parameters:
###############################################################################

  DomainName:
    Type: String
    Description: The domain name.

ryanflorence

import React, { useEffect } from "react"
import useFetch from "./useFetch"

export default function ProcessingPurchase({
  send,
  context: { workshopData, ticketsToPurchase, stripeToken }
}) {
  let [charge, error] = useFetch("/purchaseWorkshop", {
    workshopId: workshopData.id,
    ticketsToPurchase,

kitze

import {
  formatDistance,
  isAfter,
  isBefore,
  endOfDay,
  startOfDay,
  isSameDay,
  isSameSecond,
  isSameMinute,
  isSameHour,

threepointone

https://twitter.com/snookca/status/1073299331262889984?s=21

‪“‬In what way is JS any more maintainable than CSS? How does writing CSS in JS make it any more maintainable?”

‪Happy to chat about this. There’s an obvious disclaimer that there’s a cost to css-in-js solutions, but that cost is paid specifically for the benefits it brings; as such it’s useful for some usecases, and not meant as a replacement for all workflows. ‬

‪(These conversations always get heated on twitter, so please believe that I’m here to converse, not to convince. In return, I promise to listen to you too and change my opinions; I’ve had mad respect for you for years and would consider your feedback a gift. Also, some of the stuff I’m writing might seem obvious to you; I’m not trying to tell you if all people of some of the details, but it might be useful to someone else who bumps into this who doesn’t have context)‬

So the big deal about css-in-js (cij) is selectors.

jamiebuilds

The Challenge

Compare two (or more) tools that are trying to solve a similar set of problems, without discussing any of the following:

• Community
• Programming Language
• Documentation/Examples/Demos/etc
• Stars/Forks/Downloads/Issues/PRs/Stack Overflow Answers/etc
• Age/Maturity of tool

Rich-Harris

I've been deceiving you all. I had you believe that Svelte was a UI framework — unlike React and Vue etc, because it shifts work out of the client and into the compiler, but a framework nonetheless.

But that's not exactly accurate. In my defense, I didn't realise it myself until very recently. But with Svelte 3 around the corner, it's time to come clean about what Svelte really is.

Svelte is a language.

Specifically, Svelte is an attempt to answer a question that many people have asked, and a few have answered: what would it look like if we had a language for describing reactive user interfaces?

A few projects that have answered this question:

matthargett

First, let's note the difference in philosophy: TypeScript aims for fast analysis because you can to compile it down to JS before you can run/test it. flowtype is meant to be an async analysis that can run continuously with changes since the last analysis, or in parallel with your eslint and bundler rules. As such, flowtype's type system and analysis is not quite as concerned with speed or memory usage in service of potentially finding more bugs.

On two occasions I have tried to roll out flow in React Native applications, and on those two occasions we ended up backing out after a few weeks. Some detail: flow doesn't have a public roadmap, and what version you use is dictated by the react/react-native dependency and the annotations in react-native itself. flowtype also has some hard-coded aspects to help the analysis for React, so major updates to React itself sometimes also require updating flowtype to match. React Native upgrades then get gated based on your dependent libraries (or flow-typed) being updated

hellendag

// @flow

type ResolvedScalar = string | number | boolean | null;
type ResolvedValue =
  | ResolvedScalar
  | Array<ResolvedValue>
  | {[key: string]: ResolvedValue};
type ResolverFunction = (...args: Array<any>) => ResolvedValue;

export type ResolverMap = {