-
Notifications
You must be signed in to change notification settings - Fork 923
[GraphQL]: Optimize cache-key function #2405
Comments
Hey! I'm interested in working on this issue. Do I replace json-stable-stringify with fast-stable-stringify in package.json file and update the code usage? |
Hey, I've added some more context to the issue! Let me know if you still have questions. |
What is the definition of cache-key function? Also I see that |
We can try option 3, |
json-stringify-deterministic also looks like a very good option. There is more than 50% reduction in size of dependency. We need to replace
|
Yeah that's not bad. I'm a bit biased, though because I think if we forked it into our monorepo here and just added What do you think of going the fork route? |
Sounds good to me. I'm working on it. |
Can the forked package be in javascript? |
I've forked and updated the package to support BigInt. I've also added some tests to ensure correct behavior. |
Yes!
Are you planning to open a pull request to add it to this monorepo? That would be the ideal place for us! |
Working on adding it to monorepo. |
Because there has been no activity on this issue for 7 days since it was closed, it has been automatically locked. Please open a new issue if it requires a follow up. |
Problem
Since
fast-stable-stringify
doesn't supportbigint
natively, we've had to usejson-stable-stringify
in the GraphQL library.However,
json-stable-stringify
, is huge, and we shouldn't introduce this bloat to the codebase.Proposed Solution
We can do one of three things:
bigint
.fast-stable-stringify
and addbigint
support.bigint
support intofast-stable-stringify
.The text was updated successfully, but these errors were encountered: