suggestions

[yaacovCR]

includes:

1. changes just to reduce the diff
2. use of Maybe for some of our exported helper functions to match rest of our API
3. reverts some of my previous suggestions revolving around collectFields() => i was under the mistaken assumption that we never needed to pass maskSuggestions to collectFields, but because of fragment arguments, we might have complex inputs and we might need to mask suggestions
4. errata

[github-actions]

Hi @yaacovCR, I'm @github-actions bot happy to help you with this PR 👋

Supported commands

Please post this commands in separate comments and only one per comment:

• @github-actions run-benchmark - Run benchmark comparing base and merge commits for this PR
• @github-actions publish-pr-on-npm - Build package from this PR and publish it on NPM

[yaacovCR]

I'm not totally sure about the argument ordering, I'm not happy to separate variableValues and fragmentVariableValues, and I'm not happy to put maskSuggestions earlier, because that would be a breaking change, so I settled on putting maskSuggestions later, which is fine, except that if we ever revert the fragment arguments experiments, that would end up being a breaking change... Now, I don't ==think== we are going to revert it.... thoughts on that minor issue?

[JoviDeCroock]

I'm sorry but in general this feels very nitpicky about argument ordering 😅 all for avoiding a breaking change and maybe it's better to even use options consistently in collectFields as well but all the other changes are styllistic