* Hacked insomnia lib package to get Insomnia's networking in tests
* Some small tweaks
* Got it mostly working
* Tweak
* Fix
* Fix pkg
* Fix some things
* Add comment
* Comment out log
* Some tweaks after doing a self code review
* Fix test
* Update app name for `insomnia-send-request`
* Update package-lock
* Update package-locks
* Fix tests
* Add gitignore
* Fix tests hopefully
* Fix accidental dep deletions
* Fix tests again
* Mock for all tests
* Update tests again
* Don't compile for Electron for tests
* Update release scripts to disable tests
* add key combinations for dev tools hotkey
* add Dev Tools accelerator to View menu remove from Develop menu
* remove changes from hotkey.js
Co-authored-by: Gregory Schier <gschier1990@gmail.com>
Co-authored-by: Opender Singh <opender94@gmail.com>
* Update test fixtures and allow sendRequest() callback for testing
* Change runTests() to take in test src instead of a file
* Fix looping
* Fix tests and write temp test files into folder
* Fix Flow type for mocha
* Add multi-switch component, refactor radio group, and add succeess icon
* Fix dark theme for storybook
Co-authored-by: Mike Ellan <52717970+sonicyeti@users.noreply.github.com>
* Add
* Update
* Remove extra peer dep
* Remove extra peer dep undo
* Undo stuff
* Convert two components (validation)
* Undo packed dep change
* Fix for react-dom alias to @hot-loader/react-dom (#2292)
Co-authored-by: Gregory Schier <gschier1990@gmail.com>
This adds a new trigger condition for re-sending a request for the
`response` plugin called "When Expired". This condition allows
specifying a maximum age of a response to use. This is very useful when
configuring a hierarchy of environment variables that ultimately depend
on an auth token that needs to be refreshed periodically.
Previous workarounds are:
1. Use "always refresh". This fails in cases where you must use the same
auth token since it is refreshed for every request.
2. Use "no history" or "never" and manually refresh the token. This is
inconvenient and requires pinning the token.
Alternative solutions are:
1. Add more sophisticated logic to determine when the token needs to be
refreshed (e.g. refresh if the current request returns a `401` status
code)
2. Write a custom response plugin to time out the token. I believe this
functionality is small enough and general enough to be contributed
back generally.
Fixes#1972
