Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
How to test plugins?
See original GitHub issueYet another question 😉 I just created my first tiny httpyac plugin \o/. Same time its my first JS project ever, too.
https://github.com/rngtng/httpyac-plugin-yaml-body
No TS and all that jazz (yet) - but I wanted at least to test it before releasing. I got the test framework up and running, but I wonder how can I ensure cli.execute to load the plugin for testing? I thought of a deeper layer than the cli which could be evoked and load the plugin? Any ideas?
If you have the time pls check https://github.com/rngtng/httpyac-plugin-yaml-body/blob/main/test/index.test.js#L12-L17. Thanks
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:14 (14 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
And there it is https://www.npmjs.com/package/httpyac-plugin-yaml-body!!! wuhu 😃
Updated: https://github.com/rngtng/httpyac-plugin-yaml-body/pull/2
I kept one high-level integration test, moved the edge cases to unit test. I c&p you
getHeaderto stay independent as much of the inner httpyac implementation. Next setting up pipeline and publish npm 😛