Live data from Hacker News

Viewing profile — phryneas

phryneas

HN member
Joined
Mon, Mar 05, 2018, 11:06 PM UTC
HN karma
17
Public activity
23 items

About phryneas

No profile information was provided.

Recent public activity

  1. comment
    Comment #47309476

    Isn't that equal to just returning `{ typename: "MyTypeName", id: 123 }` from a resolver and then `graphql-js` just running the field resolvers on the `MyTypeName` type as needed? …

  2. comment
    Comment #45769898

    I'm an engineer on the client team, so I'm a bit fuzzy on the Apollo Server details and history, so please bear with me :) I guess you're talking about [Safelisting Persisted Queri…

  3. comment
    Comment #45759997

    Huh, that's an interesting take - honestly I don't really know what to do about that :/ It's definitely not our intention to send that message - Apollo Client should be a good fit …

  4. comment
    Comment #45759577

    Hi there, Apollo Client maintainer here! Great to see more GraphQL projects sprouting out there :) If I may ask, are there any things that are currently missing in Apollo Client to…

  5. comment
    Comment #36444157

    You can just call the `cookies()` or `headers()` function in every server component in the app router?

  6. comment
    Comment #36444148

    API routes are nothing new, and not a big part of the new App router (also, called "route handlers" there). Are you confusing features here?

  7. comment
    Comment #34286759

    Hi, RTK Query author here - from taking a skim at the code, you really went deep into our documentation. Looks good! :) Many people here tell you "study", others tell you "don't". …

  8. comment
    Comment #26388950

    It doesn't seem verbose to me. Have you looked into those docs above? You define a reducer and an action creator is automatically generated. String action types are an implementati…

  9. comment
    Comment #26388198

    With a lot of hand-written boilerplate, many required manual optimizations and performance that will in the best case be equal but often doesn't even get close. Context cannot rere…

  10. comment
    Comment #26388155

    That would be the "observing" approach I described. The upside of an action-based (signalling) approach is that you have a better time separating concerns as actions (if used corre…

  11. comment
    Comment #26388111

    That page introduces one tool after another, replacing all those external tools with the officially recommended Redux Toolkit that wires all of them up for you. In the end you are …

  12. comment
    Comment #26387262

    That does not sound like you are up-to-date with what the official redux tutorials currently recommend for writing modern redux. https://redux.js.org/tutorials/fundamentals/part-8-…

  13. comment
    Comment #26387194

    Just leaving Kent's more up-to-date opinion on modern Redux with the official redux toolkit here: https://youtu.be/xJpNIbJYK8Y?t=1523 You are right, if all your state is "cache sta…

  14. comment
    Comment #26386998

    Shameless PR to update the "side-by-side" comparison on that page to an actually recommended style of Redux: https://github.com/wire-ts/wire-ts.github.io/pull/2

  15. story
  16. story
  17. story
  18. story
  19. story
  20. comment
    Comment #16689507

    The point of using immutable in this case is to prevent mutating the state by accident as a side-effect of another action. I know that react-redux will only rerender if things chan…

  21. comment
    Comment #16687667

    immutability of redux state is convention, but not enforced within redux. This example is react state, but the same problems arise with redux: https://twitter.com/brayoh_k/status/9…

  22. story
  23. story