Closed llc1123 closed 2 years ago
Anything blocking this PR? @StarpTech
Time to review :smiling_face_with_tear: I'll try to review it in the next days.
I would love to use this! Any updates on blocking review @StarpTech ?
@llc1123 please fix the conflict. I'm going to review it in the next days.
@StarpTech fixed.
Really looking forward to this PR - the memoization shortcoming that this PR addresses has been a blocker for us.
Did you run the benchmarks?
Updated. @StarpTech
Any updates @StarpTech ? Would love to use these changes.
Any updates @StarpTech ? Would love to use these changes.
same , waiting on this update 👍
@StarpTech Any updates? Or should I fork for my use case?
@tdipadova3rd sorry for the delay. I'll review and merge this PR this week :crossed_fingers:
@llc1123 I appreciate the refactoring, but you touched way too many places which aren't related to the issue. This makes reviewing hard.
The changes are in separate commits and should be easy to be figured out.
The changes are in separate commits and should be easy to be figured out.
That's not what I meant.
@llc1123 in order to close the issue. Please create another PR that contains only the fix for https://github.com/StarpTech/apollo-datasource-http/issues/34. The next step is to avoid a performance drop of ~15%. I'll help you with that.
What's the status on this? Still chomping at the bit to cut over to this data source...
I have migrated to apollo server v4 and this code is no longer maintained.
Fixes #34