Sam Selikoff
Sam Selikoff
It does work, perhaps you have the wrong reference? You need to access it from the server instance: https://miragejs.com/repl/v2/daeadd1023
Did you see you need to pass the `{ trackRequests: true }` option to `createServer()`?
can I see the creation code? Might be simple as ```js server.create('report', { users: [ server.create('user') ] }) ```
I haven't, haven't had much time for mirage support lately :( Might have more luck asking in our Discord.
I'm still using Mirage for my personal projects and our consulting clients are also using it, but I haven't been actively developing it due to sustainability reasons. I've been noodling...
But to answer your question I do not want to be a blocker to the community and am more than happy to help with anyone wanting to carry the flag...
Yeah woof that's rough. I do hate when libs make landgrabs like this, especially when it's not called out. Extremely frustrating to stumble upon + debug (so thanks for tracking...
How are you calling `createServer`? It should work in production as long as you aren't only calling it conditionally based on process.env.NODE_ENV
Hey Alina – so sorry you're running into these issues! Any chance you have a repo you should share that reproduces your problem? That would be the fastest way for...
I don't think so atm :/ Here's the logic currently: https://github.com/miragejs/miragejs/blob/master/lib/serializer.js#L691-L696 Best bet would probably be to override one of those methods in your own app. Or work on a...