Tweetovi

Blokirali ste korisnika/cu @ryanflorence

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @ryanflorence

  1. I sometimes get misunderstood that I think testing is a waste of time, but it's so easy to slip into thinking that passing tests means a good product. Your tests will never mean it's a good product. They only mean you implemented it the way you meant to--but not that it's good.

    Prikaži ovu nit
    Poništi
  2. I wish programmers worried about accessibility with the same righteous vigor as testing.

    Prikaži ovu nit
    Poništi
  3. proslijedio/la je Tweet
    prije 4 sata

    See my latest article on how useEffect(fn, []) is not the same as componentDidMount.

    Poništi
  4. proslijedio/la je Tweet
    1. velj

    The core of react-router v6 is 357 lines of code, excluding comments and __DEV__ blocks (which are mostly propTypes). Should be able to read it in an afternoon, if you're curious 👀

    Prikaži ovu nit
    Poništi
  5. 1. velj

    Sometimes I remember that Travis Barker was "The Baron von Tito" and it's had to believe.

    Poništi
  6. 1. velj

    Can't stop working. Send help.

    Poništi
  7. 31. sij

    We have two people who work full-time on our open source. Without your support of our workshops (NYC, Boston, tickets on sale rn!): and our online courses: This stuff would absolutely not happen. Thank you for your support!

    Poništi
  8. proslijedio/la je Tweet
    31. sij

    📣 Also published this week: Reach UI v0.8.0 🔥 Meet our newest additions: - reach/accordion - reach/checkbox - reach/disclosure Thank you for your continued support! You all rock. Docs 👇

    Prikaži ovu nit
    Poništi
  9. proslijedio/la je Tweet
    31. sij

    📣 Just published: React Router v6.0.0-alpha.0 👀 - Relative routes + links - Nested routes ala v3 - Automatic route ranking - Suspense-ready navigation - Object-based route config with useRoutes Our most ambitious release since v4 🤘 Release notes 👇

    Prikaži ovu nit
    Poništi
  10. 31. sij

    Just got a work email from "Michael Ryan". This is going to be a confusing email thread.

    Poništi
  11. 31. sij

    OSS devs shipping APIs they don't like but don't want to deal with the github issues

    Poništi
  12. 31. sij

    All I know about yarn 2 is that people are opening issues on our repos saying that our packages are broken.

    Poništi
  13. 30. sij

    Assuming you can choose lazy load behavior on a per route basis: "Routes should be lazy loaded by default."

    Poništi
  14. 30. sij

    > Can you jam with the console cowboys in cyberspace

    Poništi
  15. 30. sij

    Welcome to part of my talk 👯‍♂️ See you in March, my first trip of the year! With all this management I hope I can still talk about code 🤧

    Prikaži ovu nit
    Poništi
  16. 30. sij

    OR YOU CAN LIVE ON THE EDGE and send it up through useLayoutEffect and then you get it for the initial DOM commit--but it won't work on the server if that's your jam. For things like popover content, it works wonderfully, cause popover content don't render on the server anyway.

    Prikaži ovu nit
    Poništi
  17. 30. sij

    Unless the Parent doesn't need that "config" (props) for the initial render. Then you can send that stuff up through context in useEffect and deal with it after the first render. Like a video tag. You gotta load that stuff async anyway, first render doesn't matter.

    Prikaži ovu nit
    Poništi
  18. 30. sij

    Problem is the Parent needs to inspect `props.children.props` (that's the config!) but it can't because `children.props` is empty because of the wrapping. They need to be static. Unless...

    Prikaži ovu nit
    Poništi
  19. 30. sij

    Difference in React components vs. elements though is that you *can* do this: <video> <WrapsSourceElement/> </video> But this has limitations: <Parent> <WrapsConfigChild/> </Parent>

    Prikaži ovu nit
    Poništi
  20. 30. sij

    <video controls> <source src="file.mp4" type="video/mp4"> <source src="file.ogg" type="video/ogg"> No video! </video> This element doesn't "render" the children. They're just config for the parent! Don't be afraid of stripping props from children in React 👊🏼

    Prikaži ovu nit
    Poništi

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·