Skip to content

Enable +force-echo-filtering per interpreter and not only globally #248

@eldipa

Description

@eldipa

Describe the feature you'd like
With #245 some runners/interpreters that in pre-11.0.0 echoed stuff they would not do it anymore so +force-echo-filtering could be disabled by the user.

However #245 does not cover all the cases: it may perfectly be the case that some runners don't need the echo filtering and other do, all of them in the same byexample run.

+force-echo-filtering is per example setting or a global setting but it is clear that a per runner setting is needed.

Perhaps a new +force-echo-filtering-for=runner ?

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementsomething nice to have but it is not neither critical nor urgent

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions