fixed output - Githubissues

meet0806 commented 2 months ago

Type Of Change

[ ] New feature (non-breaking change which adds functionality)
[X] Bug fix (non-breaking change which fixes an issue)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[X] Any modification in the test cases
[ ] Any modification in the documentation

Checklist:

[X] I have read and followed the contribution guideline.
[X] I have checked to ensure there aren't other open Pull Requests for the same update/change.
[X] All the test cases pass and new modifications in the production code are 100% covered.
[X] I have made corresponding changes to the documentation.

Related Issue

Closing: #205

Description

Added given color in a stdout print statements

How Has This Been Tested?

using commands

Screenshots (if appropriate):

Additional info

janosmurai commented 2 months ago

Thanks for the PR @meet0806 !

Please note that issue #205 has a second part - implementing a pager mechanism. See for example the less unix tool as a reference. This is needed because in some cases the output of these commands can be a huge list and we got some feedback that a paging mechanism could help in navigation.

Hacktoberfest only starts on the first of October, so if you'd like this PR to count, I won't approve this issue until then.

meet0806 commented 2 months ago

Hacktoberfest only starts on the first of October, so if you'd like this PR to count, I won't approve this issue until then.

Okay, till then I will add changes related to pager

janosmurai commented 2 weeks ago

Hi @meet0806

Do you still work on this issue?

meet0806 commented 2 hours ago

Hi @meet0806

Do you still work on this issue?

No

axem-solutions / dem

fixed output #218