-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request]: Auto export mocks to JSON #251
Comments
Hi @bitstrider This is actually a feature we have in the pipeline and want to release in the future but due to the amount of work needed for it it might take some time. This should be done via our mimic-remote project so we can run an agent to sync to your filesystem. |
@morsdyce cool thanks for the info. Does that mean this feature is only planned to work with |
It means that we need an agent that will run on your computer that has access to the filesystem so we can write and read files. Currently we're working as the base for this on mimic-remote which is a small node server to facilitate that, we are also investigating directions like webpack plugins and chrome extensions to allow this behaviour. If you have any ideas on how we could get access to the filesystem in the least obstructive way for the user I would love to hear them! |
First off, awesome tool 馃挴 . I'm on my second project with it and so far I've enjoyed using it to keep the flow going when working through front-end.
So I have my current project set up to automatically import my mocks, and will re-export from time to time as I add more or update existing mocks. But then recently I forgot to do this and ended up losing some mocks to the void. No big deal since it was not a lot of work to rewrite, but it would be great in the future to have an extra feature to auto export so I can prevent this from happening again.
Thoughts?
The text was updated successfully, but these errors were encountered: