🦋 Changeset detected

Latest commit: e063e58

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Codecov Report

Attention: Patch coverage is 0% with 4 lines in your changes missing coverage. Please review.

Project coverage is 80.99%. Comparing base (f295b3e) to head (e063e58).

@@            Coverage Diff             @@
##             main    #1390      +/-   ##
==========================================
+ Coverage   80.95%   80.99%   +0.03%     
==========================================
  Files          54       54              
  Lines        2211     2210       -1     
  Branches      652      657       +5     
==========================================
  Hits         1790     1790              
+ Misses        417      416       -1     
  Partials        4        4              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Looks like status/index.ts wasn't covered by tests before, so adding more lines here seem to caused more missing coverage. Should I add some sort of test to cover it?

I've discussed with @jakebailey and @benmccann of some alternative table libraries:

• cli-table3 - tradeoffs:
  • No word wrapping for small console widths
  • No direct option for table indenting (can be workaround with string manipulation)
• table-layout - tradeoffs:
  • Larger dependency graph, but there's a PR to slim it down
  • Has a limited set of styling options

Other libraries like console-table-printer seem to also share the same or more tradeoffs of the above two libraries. Or libraries like cliui could work but they're CLI focused.

In a sense, the only thing that --verbose does is print the information about related changesets. The table layout is kinda nice at presenting this but maybe it's unnecessary? Can we think about a different of presenting this data that would result in a simpler code and that wouldn't suffer from wrapping limitations/complexity?

Perhaps a list form like this?

A bit similar to non-verbose mode but with the added version and changeset files.

It works for me, I think. Since a lot of changesets can be related to any particular release, I wonder if this should be a bullet~ list or just a comma-delimited list. None of them is perfect as it all depends on how many packages, changesets, etc u have... Let's just roll with what u have above.