| 2024-05-02 16:13:22 |
James Carroll |
description |
When running `snap info $SNAP`, a summary of output is presented to the user, including the `Contact:` field. Historically, there used to be less fields and `Contact:` was used from everything to personal email addresses to bug trackers.
Snapd now supports additional fields, such as `issues`, `source code`, etc, which are promimently displayed on snapcraft.io/$SNAP - but not shown by default in the CLI without running `snap info --verbose`.
Is this behaviour intentional? In my opinion, these links are promiment in the Web UI for a reason and should be similarly promiment on the CLI.
I'd believe the change would be removing the verbosity check here:
https://github.com/snapcore/snapd/blob/fe6e39a2bc9d5107a329eb967caf4a2d9c843ccf/cmd/snap/cmd_info.go#L389
And updating any failing tests to compensate for the new behaviour.
Would the snap gang be happy with me proposing a PR to remove the need for `--verbose` for these fields :)? |
When running `snap info $SNAP`, a summary of output is presented to the user, including the `Contact:` field. Historically, there used to be less fields and `Contact:` was used from everything to personal email addresses to bug trackers.
Snapd now supports additional fields, such as `issues`, `source code`, etc, which are prominently displayed on snapcraft.io/$SNAP - but not shown by default in the CLI without running `snap info --verbose`.
Is this behaviour intentional? In my opinion, these links are prominent in the Web UI for a reason and should be similarly prominent on the CLI.
I'd believe the change would be removing the verbosity check here:
https://github.com/snapcore/snapd/blob/fe6e39a2bc9d5107a329eb967caf4a2d9c843ccf/cmd/snap/cmd_info.go#L389
And updating any failing tests to compensate for the new behaviour.
Would the snap gang be happy with me proposing a PR to remove the need for `--verbose` for these fields :)? |
|
