https://www.prisma.io/ logo
Join Slack
Powered by
# prisma-whats-new
  • s
    yeah, I totally agree
  • s
    on the one hand they make it easier to co-locate requirements, but on the other hand they kinda make your UI more coupled to the data loading system
  • m
    right...
  • s
    in our production app we use fragments very sparingly
  • s
    in particular, we use them to share fields between the query that initially fetches data, and the mutation that refetches it
  • s
    so that we update all of the necessary fields
  • s
    we don't really do the whole fragment-per-component thing
  • s
    but I think it can be useful to reduce action at a distance. maybe there's some happy medium where you have a reasonable number of fragments, such that most of your components are still "pure" or whatever, but your queries are not super huge
  • m
    i'm not sold on the huge queries being an issue, since you can break it down by component into smaller queries
  • m
    and put it in a separate file
  • s
    yeah, fair enough
  • s
    especially once static type generation for query results is more common, it will be easy to make sure the query actually fetches all of the data your components need
  • s
    Very good point @sashko! Is there an official standard emerging for request "batching"?
  • c
    hey what does this header do? 
    x-graphcool-source
  • s
    Hey @cartogram! This header is just used that we can see when you ran the example project to update your onboarding status. We should definitely add some comment for that!
  • c
    Oh okay, yeah no worries.
  • s
    unfortunately there is no standard I know of
  • c
    Hey, are there any filter operations available on relations?
  • s
    Hey Chris! This is a feature we have planned. It would be very helpful if you could open a feature request and describe your use case here https://github.com/graphcool/feature-requests/issues
  • c
    Thanks will do
  • s
    Excellent! Just to be sure - you do know about the scalar filters, right?
    Copy code
    {
  allUsers(filter:{name_contains:"Anders"}){
    routes(filter:{level:EASY}){
      description
    }
  }
}
  • c
    Yup, I was trying to filter based on whether the row had child elements. Will set a boolean field for now to work around.
  • s
    Glad you found a workaround! This feature is on our roadmap for November: https://github.com/graphcool/feature-requests/projects/1
  • c
    Awesome
  • l
    @sorenbs: awesome way of organizing the roadmap, by the way
    👍 1
    🙌 1
  • m
    I see auth0 is done. Woot!
    🎉 1
  • c
    guys would you recommend react or angular2? i've been using angular1 and loved it but not quite sure which way to go for future apps. i've noticed react seems to have a lot more attention and support now.
  • s
    In my opinion Angular 2 is so different to Angular 1 that the learning curve is the same no matter what you choose, so that shouldn’t be a factor.
  • s
    And we picked React for good reason 😄
  • c
    yes Angular 2 just seems so completely different from v1, that was frustrating
1...333435...637Latest