search

invertase / melos

🌋 A tool for managing Dart projects with multiple packages. With IntelliJ and Vscode IDE support. Supports automated versioning, changelogs & publishing via Conventional Commits.
https://melos.invertase.dev/~melos-latest
Apache License 2.0
1.08k stars 193 forks source link

request: log output is the same or similar even if the `-c` option of `melos analyse` is greater than or equal to 1 #668

Closed koji-1009 closed 4 months ago

koji-1009 commented 4 months ago

Is there an existing feature request for this?

Command

melos analyze

Description

The melos analyze command, added from v5, logs differently for -c 1 and -c 2.

-c 1 case

$ melos analyze -c 1
Building package executable...
Built melos:melos.
$ melos analyze
  └> dart analyze
     └> RUNNING (in 3 packages)

--------------------------------------------------------------------------------
conventional_commit:
Analyzing conventional_commit...
No issues found!
conventional_commit: SUCCESS
--------------------------------------------------------------------------------
melos:
Analyzing melos...
No issues found!
melos: SUCCESS
--------------------------------------------------------------------------------
melos_workspace:
Analyzing melos...
No issues found!
melos_workspace: SUCCESS
--------------------------------------------------------------------------------

$ melos analyze
  └> dart analyze
     └> SUCCESS

-c 2 case

$ melos analyze -c 2
Building package executable...
Built melos:melos.
$ melos analyze
  └> dart analyze
     └> RUNNING (in 3 packages)

--------------------------------------------------------------------------------
Analyzing conventional_commit...
Analyzing melos...
No issues found!
No issues found!
Analyzing melos...
No issues found!
--------------------------------------------------------------------------------

$ melos analyze
  └> dart analyze
     └> SUCCESS

It would be nice if the two were the same, or at least easier to understand SUCCESS per package.

Reasoning

In environments with many packages (e.g. plus_plugins), it is suitable to set many -c. And because it is an environment with many packages, it is nice to have a log output that makes it easy to check the success or failure of each package.

Additional context and comments

No response

jessicatarra commented 4 months ago

It's a logging output issue, the concurrency is actually working fine, but the logs are not being displayed properly to the user, showing the correct information