Make `mergeAST` opt-in only
See original GitHub issueAs per discussions with @IvanGoncharov, the utility/mergeAst
function looks like a good candidate for inclusion in graphql-js
itself, however it shouldn’t be mutating AST directly. Instead, we will refactor it to use the visit
function to accomplish this, and then open a PR to graphql-js
. This is just a placeholder for the forthcoming PR
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:5 (5 by maintainers)
Top Results From Across the Web
View git log without merge commits - Stack Overflow
use git log --author=<name> --no-merges. Additionally the --first-parent option may give useful result for you: --first-parent Follow only the first parent ...
Read more >Merging | Merge Dragons Wiki | Fandom
However, there are many merges that create more than just 1 object. Merging Magic Mushroom Caps may create Magic Shroom Stalks, which is...
Read more >Merge Dragons How To Build Tips Guide - YouTube
Merge Dragons! ✌ https://www.youtube.com/channel/UCuUgwB9Y_ll2Hlm_b1Msv5Q/join ...
Read more >Mail merge - Streak Support
See all of your mail merges in the Sequences list ... For example, you can create a filter that only includes recipients who...
Read more >Merging Actors - Unreal Engine Documentation
By default, this method merges all selected Static Mesh Actors, creating one ... Disable this option to save memory if the merged mesh...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yeah, it’s great for pinning down issues in large queries as you can do proper bisection which is hard with fragments.
💯 It would be unfair to remove it entirely; let people opt in if they’re aware of the issues. In v1.0 this will be a plugin (quite likely a non-default one, I think we should keep our default set of buttons to a minimum).