-
Notifications
You must be signed in to change notification settings - Fork 5
Open
Labels
UXNot broken, but frustrating/unclear for usersNot broken, but frustrating/unclear for usersenhancementNew feature or requestNew feature or request
Description
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
Labels
UXNot broken, but frustrating/unclear for usersNot broken, but frustrating/unclear for usersenhancementNew feature or requestNew feature or request