-
Notifications
You must be signed in to change notification settings - Fork 7
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
ladislas/bugfix/ut corejpeg missing include #1151
ladislas/bugfix/ut corejpeg missing include #1151
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #1151 +/- ##
========================================
Coverage 96.00% 96.00%
========================================
Files 138 138
Lines 3253 3253
========================================
Hits 3123 3123
Misses 130 130
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
File comparision analysis report🔖 Info
Click to show memory sections
📝 SummaryClick to show summary
🗺️ Map files diff outputClick to show diff listNo differenes where found in map files. |
File comparision analysis report🔖 Info
Click to show memory sections
📝 SummaryClick to show summary
🗺️ Map files diff outputClick to show diff listNo differenes where found in map files. |
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.
It is better in my opinion to keep it the most explicit possible the origin of some used classe/interface/variable (e.g. interface::STM32Hal
, interface::File
, JPEGImageProperties
, jpeg::JPEG_SOI_MARKER
) and not popping from nowhere.
Same from standard libs, #include <array>
is indeed not relevant in header file but it is used in source and might lead to unknownstd::array
warning/error
cc86c0d
to
aa00c55
Compare
aa00c55
to
aa7386b
Compare
Kudos, SonarCloud Quality Gate passed!
|
Fix issue spotted at: