You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 16, 2023. It is now read-only.
Since all the recorded requests might contain sensitive data (such as credentials), I encrypted all the fixtures/* files before pushing them. Right after having processed to this gpg encryption, a few error started spawning and I realized from your source code that you actually expect each file from the fixture directory to fit your request/response model. Could we think about removing *.gpg files from readdirSync result before being parsed ? I can take care of it for sure if you agree with it.
By the way thank you for this tool, it's a nice and useful project for sure ! 👍
Best regards
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
Since all the recorded requests might contain sensitive data (such as credentials), I encrypted all the
fixtures/*
files before pushing them. Right after having processed to this gpg encryption, a few error started spawning and I realized from your source code that you actually expect each file from thefixture
directory to fit yourrequest/response
model. Could we think about removing*.gpg
files fromreaddirSync
result before being parsed ? I can take care of it for sure if you agree with it.By the way thank you for this tool, it's a nice and useful project for sure ! 👍
Best regards
The text was updated successfully, but these errors were encountered: