Props to @benjamn for helping me land some features in graphql-tools removing a *lot* of cruft in @bustle's graphql api. https://github.com/apollographql/graphql-tools/issues/616 …
Contributing upstream is always worth it.
-
Show this thread
-
I started by writing the feature in our app. It's not a big deal, but its helpful, so it makes sense to do it. But.. I really want our app to be boring. Without all the little helpers and customizations you end up making over time.
1 reply 0 retweets 1 likeShow this thread -
I found the issue already exists, someone from my team opened it a long while ago! Props to
@southpolesteve1 reply 0 retweets 1 likeShow this thread -
It took a lot longer to go through review and get feedback in a project that I'm unfamiliar with. But the
@apollographql team has a really smooth process and guided me through it. That obviously took some effort to set up.1 reply 0 retweets 3 likesShow this thread -
I was also really scared to make api changes in a large project for a feature that I want. But I asked and they were for it. I just had to ask. Better for me is better for anyone in my situation.
1 reply 0 retweets 0 likesShow this thread -
All this is to say, while I could have landed this *much* quicker in our api, I'll *never* have to do it again because I got it in the tooling. Contributing upstream is always worth it.
1 reply 0 retweets 1 likeShow this thread
Thanks for making it happen!
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.