Initialization option to specify mock response for page load scenarios

[kgoggin]

The process for creating an intercept and specifying a mock result is a little tricky to work with if you're trying to mock a query that runs on page load, especially if the Apollo link is being lazily loaded. What if we could specify some intercepts/mock responses that we want in place at the point that we initialize the Apollo link, so they were ready from the outset?

I think I'm envisioning that CreateLaikaLinkOptions could be extended to include an array of intercept + mock definitions, that would be set up immediately.

The downside here is that you don't have a reference to the intercept anywhere to call further methods on it, but I think those are mostly helpful in testing situations, and I envision this being used for simulating server responses in an actual running app. Maybe there'd be a way to expose the intercepts via the main toolkit somehow so that you could still manipulate them?

[bbrzoska]

I think the idea is solid! The only thing I would think about is somehow abstracting the storage. Apollo Client can be used outside of web, for example in react-native or for SSR, so internally tying it to use either localStorage or query string would break those use cases. Extending CreateLaikaLinkOptions seems like a good way to go about that, since it leaves actual implementation of storage to the end user.

[donovan-yohan]

Has there been any progress or update on this front? Also curious about current workarounds for getting Laika to work for queries that run on initial page load. Thanks so much!

[bbrzoska]

Hi @donovan-yohan! We haven't made any progress on this front, but we are accepting discussion about possible implementation and/or PRs!

[donovan-yohan]

I opened a PR related to this and would love to get the ball rolling on getting this feature into Laika :D