Make Phinx less verbose by default
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 4.5k
- Forks
- 884
- PR merge metrics
- No merged PRs in 30d
Description
In normal usage it feels like I've added -v to all commands, as Phinx always prints lines about the config file, file format, paths, etc. I would suggest to bump the verbosity levels of those messages (or all, therefore). I can submit a patch for that, but I'm not sure if this would be a "breaking" change?
There's a while I don't use Phinx, but I don't recall all those "headers"... Was it always like this? Or is it a "recent" change?
In red, what seems unnecessary for routine commands, and in green what I'm really expecting of output from phinx status.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the verbose output from routine Phinx commands, especially phinx status, and locate the CLI handling for message verbosity and headers. Done means routine output keeps the expected status information while config, format, and path details appear only at a higher verbosity level; also verify the behavior change is documented as potentially breaking.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100