Skip to content

Improve logging output #953

@ben-edna

Description

@ben-edna

Sometimes an action leads to multiple logging statements, such as local changes during a fetch or a patch.
Introduce a concept that has one logging line that metnions the project and the action it is performing or goal it is achieving and make sub statements under it:

Before

Dfetch (0.11.0)
  CumulativeMovingAverage: Fetched cumulativemovingaverage/v0.0.1
  CumulativeMovingAverage: Updating patch Core/Modules/Patches/CumulativeMovingAverage.patch
  CumulativeMovingAverage: Fetched cumulativemovingaverage/v0.0.1
successfully patched 1/2:        b'CumulativeMovingAverage.c'
successfully patched 2/2:        b'CumulativeMovingAverage.h'
  CumulativeMovingAverage: Applied patch "Core/Modules/Patches/CumulativeMovingAverage.patch"

After

  CumulativeMovingAverage: updating patch
      ├─── Fetched cumulativemovingaverage/v0.0.1
      ├─── Updating patch Core/Modules/Patches/CumulativeMovingAverage.patch
      ├─── Fetched cumulativemovingaverage/v0.0.1
      │    ├─── successfully patched 1/2:        b'CumulativeMovingAverage.c'
      │    └─── successfully patched 2/2:        b'CumulativeMovingAverage.h'
      └─── Applied patch "Core/Modules/Patches/CumulativeMovingAverage.patch"

Metadata

Metadata

Assignees

No one assigned

    Labels

    UXNot broken, but frustrating/unclear for usersenhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions