Ian VanSchooten

Sounds like a good idea to me, without looking into any of the feasibility or implementation details. Can't imagine it would be too terribly hard...

Miragejs is not very maintained currently. If it's important to you that this gets fixed, I'd suggest digging in to the code and putting up a PR. I'll be happy...

I rebased this PR, and I think the typescript failure is unrelated. I think the only thing that's missing from the PR is an improvement to our TS type here:...

That's an interesting thought. Personally, I like to allow my components themselves to fetch the data that they need, rather than fetching everything at a screen level and then handing...

I'd be happy to review a PR that adds or fixes the type definition.

@BryanHunt Mirage is not being actively developed any longer by the original creator. I hang around and try to help out, and am willing to review/merge a PR if someone...

I haven't given it thought up to now. My immediate response would be to release the next breaking change as 0.2.0, and let that bake for a little while, since...

@cah-briangantzler that's awesome! I think one blocker for releasing 1.0.0 would be documentation updates to reflect the new reality, including the need to specify an interception library, the current options...

I personally would be very on board with this, but I have no idea how tightly coupled mirage is to pretender. From what I can tell, @samselikoff wouldn't be opposed...

@cah-briangantzler those look like side-effect imports, since they are not actually returning any values. The order of side-effect imports can indeed matter, since they might be modifying something on the...