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
Other tools in the JavaScript ecosystem would like to be able to generate the legacy JSON format from messages, without asking their users to deal with the Go-based json-formatter - cucumber/json-formatter#13 (comment)
✨ What's your proposed solution?
Refactor the JSON formatter to just deal with messages, like e.g. the HTML one does, and the JUnit one eventually will. Do this in a way where it's reusable outside the context of cucumber-js i.e. just requiring messages and maybe query.
Probably publish it as a separate npm package
Maybe publish it in the mooted new plugin/formatter style - I'd like for formatters to be usable by any messages-emitting tool, not just cucumber-js.
⛏ Have you considered any alternatives or workarounds?
Doing nothing is another choice. But this helps the Cypress implementation and also helps move forward the new plugin/formatter system with something concrete.
🤔 What's the problem you're trying to solve?
Other tools in the JavaScript ecosystem would like to be able to generate the legacy JSON format from messages, without asking their users to deal with the Go-based json-formatter - cucumber/json-formatter#13 (comment)
✨ What's your proposed solution?
messages
and maybequery
.⛏ Have you considered any alternatives or workarounds?
Doing nothing is another choice. But this helps the Cypress implementation and also helps move forward the new plugin/formatter system with something concrete.
This text was originally generated from a template, then edited by hand. You can modify the template here.
The text was updated successfully, but these errors were encountered: