mobile-dev-inc/maestro

`maestro record` doesn't respect the `--no-ansi` flag

Open

#1,009 opened on Apr 21, 2023

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Kotlin (6,111 stars) (306 forks)batch import
buggood first issuemaestro cli

Description

While using maestro record, I noticed that it seems to ignore the --no-ansi option. When using maestro test, it works just fine. Currently using Maestro version 1.26.1.

Command that doesn't work;

maestro --no-ansi record {flow path}

Command that does work;

maestro --no-ansi test {flow path}

https://user-images.githubusercontent.com/68027680/233732432-d2217c7e-5f0f-40e8-9b71-d58386cb9f43.mp4

Contributor guide

Tech stack
kotlin
Domain
cli
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
The issue is that `maestro record` ignores the ` no ansi` flag while `maestro test` respects it. To fix, examine the CLI argument handling for the `record` command in the Maestro codebase (likely in the CLI entry point, e.g., `MaestroCommand.kt` or similar). Compare how ` no ansi` is processed in the `test` command vs `record` command. The maintainers have not yet responded, so the fix is straightforward: ensure the `record` command also applies the ANSI disabling logic.