Add formatter plugins and start reimplementing builtins #2400
+372
−146
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🤔 What's changed?
html
andmessage
) as plugins and ensure they still workThe formatter plugin has a very lean interface for now - it can listen for messages, write to the output, and access the
formatOptions
from the configuration. The idea is to reimplement more builtin formatters and in doing so find and fill limitations, and probably also build out a useful test harness or pattern for people writing their own formatters.Next candidates for reimplementing will be:
junit
(recently added, not exported)json
(because of make json formatter reusable outside cucumber-js #2239)progress-bar
(not exported, needs direct access to the stream)@cucumber/pretty-formatter
(separate package, needs access to snippet syntax)⚡️ What's your motivation?
Per #2091 we're working towards a plugin system, and that includes bring formatters into that with a leaner message-based interface.
🏷️ What kind of change is this?
📋 Checklist:
This text was originally generated from a template, then edited by hand. You can modify the template here.