* Fix issue chaining multiple requests
* refactor: use switch to prepare for leveraging exhaustiveness checking
since this will be in TypeScript soon, and this was as topical a time as any to make this change.
* fixes failing test with new behavior (and removes unused `fromResponseTag`)
* fix tests
Co-authored-by: Vincenzo De Petris <vincenzodepetris@gmail.it>
Co-authored-by: Dimitri Mitropoulos <dimitrimitropoulos@gmail.com>
Co-authored-by: Opender Singh <opender.singh@konghq.com>
* Start working on insomnia-testing package to generate Mocha code
* Moved some things around
* Integration tests and ability to run multiple files
* Fix integration tests
* Rename runSuite to runMochaTests
* Add types for test results
* Fix lint errors
* Play with Chia assertions
* insomnia and chai globals, plus a bunch of improvements
* Stub chai and axios Flow types
* Ability to reference requests by ID
* Fix chai flow-typed location
* Address PR comments (small tweaks)
* Basic UI going
* Lots and lots and lots
* Pretty-much done with the unit test UI
* Minor CSS tweak
* Activity bar triple toggle and more
* Minor tweak
* Unit Test and Suite deletion
* Bump Designer version
* Fix eslint stuff
* Fix insomnia-testing tests
* Fix tests
* lib@2.2.9
* Remove tests tab from response pane
* Hook up Insomnia networking
* Fix linting
* Bump version for alpha
* Remove extra ActivityToggleSwitch
* Remove unused import
* Add test:pre-release script that excludes CLI tests
* Less repetition
* Clean some things up
* Tweaks after self-cr
* Undo request ID tag
* Swap out switch for new activity toggle component
* Extra check
* Remove dead code
* Delete dead test
* Oops, revert example code
* PR feedback
* More PR comment addresses
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
Opender Singh