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.
Well ok it's not actively linting the docs yet - still need to fix the issues, but that's in progress!
Thanks for the note about the CircleCI config @ksaaskil, I'll look into that today
Updated our React Native example to display random cat facts 🐈 https://github.com/unmock/unmock-react-native-example
Do you guys have any frontend/MERN/React opportunities? Here's a drum machine I created in react, redux and css-grid: https://abe312-drum-machine.glitch.me/
@abe312 That's great, maybe send your cv and a brief story about yourself to jobs@meeshkan.com and we'll see!
I just had a chance to check out the
unmock-server branch - it is pretty cool stuff! If the project develops further, I wonder if/when a libunmock will 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 🤔
My apologies, it had looked like @bukharim96 's PR had passed the tests, but for some reason it was not being automatically built on our Circle CI and has several linting/installation errors. These are all quite small fixes, so we can fix them in the repo itself, but I'm wondering if there is a better way to set up safeguards against this in the future?
without
Sorry for that. So without passing secrets, I meant 😁
Enabled CircleCI builds for forked pull requests in unmock-js, did the same for unmock.github.io while I was there (ping @carolstran )
@mohsenatigh Please send job enquiries to jobs@meeshkan.com with a story of yourself, your motivation to work for us and a free-form CV, thanks!
I created a new issue that's up for grabs for anyone willing to contribute, also small PRs are welcome unmock/unmock-js#331
Are we concerned about the build on master always failing or nah? Looks like it's missing some configuration
But it also doesn't matter.
Hi there, trying to become an unmocker😅, just feel that the topic "unmock" is quite interesting. It seems that a long history in this room. I wish that I can start to contribute in a short period and get some knowledge about unmock here. Well, let me start on watching the history and documentation.
Added a PR for adding randomized behaviour to unmock: by default, it sets a fixed seed at the start of each mock generation for reproducability but that's not always desired. unmock/unmock-js#336
Also published Unmock CircleCI orb version 0.0.14, including commands for running the mock server. https://circleci.com/orbs/registry/orb/unmock/unmock Unmock server is pre-alpha and all feedback is appreciated.
Unmock server is also available via Docker if you want to try it out without installing anything https://hub.docker.com/r/unmock/unmock-server
Snyk bot found a vulnerability in unmock-server > concurrently > tree-kill and patched that in this PR unmock/unmock-js#350
The vulnerable library is however not used anymore in the project so I deleted that in unmock/unmock-js#351.
The vulnerable library is however not used anymore in the project so I deleted that in unmock/unmock-js#351.
I'm working on refactoring unmock a bit to separate the mock generation logic from the interceptor logic. This will make it easier to have "mocks on demand" without initializing the global interceptor capturing all HTTP traffic. unmock/unmock-js#355
Anyone interested in learning a bit of
lerna and 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
Any React Native experts around? 🤨 We're building towards unmock running in browser and React Native so you could use unmock for faking APIs also when developing front-end! One problem is that
unmock depends, through json-schema-faker, on json-schema-ref-parser, which in turn depends on Node.js modules http and https (https://github.com/APIDevTools/json-schema-ref-parser/blob/master/lib/resolvers/http.js#L3). unmock can 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