Added all of your notes about telemetry to the initial doc, thanks!
Also @ksaaskil question for you re: some of our tests. I'm running with this idea of adding more meaningful placeholders and stumbled across this test in the unmock-node package: https://github.com/unmock/unmock-js/blob/dev/packages/unmock-node/src/__tests__/index.test.ts#L38-L44
What is this testing for exactly? I'm trying to think of a better replacement for "foo" (maybe var, data, whatever) but also curious about whether or not we actually need this test.
unmock-serverbranch - it is pretty cool stuff! If the project develops further, I wonder if/when a
libunmockwill be in order? It makes sense to start with NodeJS as that is our most developed library, but at a certain point, having the whole stack in TypeScript seems like a disadvantage if the goal is to deploy it as a stand-alone or embedded entity. I'm wondering how we could test that out 🤔
lernaand seeing how to create a new package under
unmock-js? :) I created an issue to extract common types into a new package and included instructions how that should work. unmock/unmock-js#357
json-schema-ref-parser, which in turn depends on Node.js modules
unmockcan run fine without these, but the Metro bundler used for bundling React Native crashes because the modules cannot be found. Does anyone have insights how to best solve the issue? I've written more about it in this PR unmock/unmock-react-native-example#3