-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Log refactor - Table logging features #2984
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
First wave
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
second wave
…dudes/table-layout
…feature/dudes/table-layout" This reverts commit 8f74cfa.
…nto feature/dudes/table-layout
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #2984 +/- ##
===========================================
+ Coverage 53.56% 53.70% +0.14%
===========================================
Files 1003 1010 +7
Lines 85295 85637 +342
===========================================
+ Hits 45685 45992 +307
- Misses 39610 39645 +35 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
New batch! I hope it will be the last one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All good to me!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All good to me!
{ | ||
m_errorsMsg.push_back( splitErrors ); | ||
} | ||
m_errorsMsg.push_back( msg ); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe inline it now? (Or even remove it: it seems to be used once for a push_back
...)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
function deleted
static constexpr char m_sideCross = '+'; | ||
/// symbol to delimit a table column | ||
static constexpr string_view innerCross = "+"; | ||
static constexpr char m_innerCross = '+'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where are m_sideCross
and m_innerCross
used?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They aren't used anymore, they are just for customisation purpose
if we want to have a table with this style +-----+
, we can use them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As there is no longer code that use these contants, you must remove it. If someone will need to change the style of the tables, he will re-write them.
Keeping them would be confusing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, it's removed
…DEV/GEOS into feature/dudes/table-layout
This PR is the first one of a work in collaboration with @MelReyCG that aim to standardize logs and make them more readable.
Today's logs are complicated to read:
This PR aim to help to format the logs in a clearer way by providing table drawing :
This feature will be used in a first time for the well data output. According to the
well control
log level, the column of previous and next element can be displayed.An example of the refactored Well Log:
Dumping 5 Elements into Log and CSV
1. Data collection
2. Format the data
3. Dumping the data
Log Output
An example of current well log, 3 elements displayed
With the new log