Recognize Ceedling 1.1.0 bullet point test listing report

[mrtumnus]

Accept test lines in bullet point format, produced starting in Ceedling version 1.1.0.

Fixes #10

[jake-kim-sndk]

@mkarlesky VS Code extension became useless due to this careless change made 2 months ago.
ThrowTheSwitch/Ceedling@22372a3#diff-ac6a2a9e0178323fec1eced6fbdd08c509565f16a66de3a469342b92bf8a361bL90-R101

       if files_list.size > 0
-        files_list.sort.each { |filepath| puts " - #{filepath}" }
-        puts "File count: #{files_list.size}"
-        puts "Note: This list sourced only from your project file, not from any build directive macros in test files."
+        files_list.sort.each { |filepath| loginator.console(" • #{filepath}") }
+        loginator.console("File count: #{files_list.size}")
+        loginator.console("\nThis list sourced only from your project file, not from any build directive macros in test files.\n\n", LogLabels::NOTICE)
       end

This line here should've been updated together when changing logging formats, or at least should've made them backward compatible.

[mkarlesky]

@mrtumnus @jake-kim-sndk Thank you for these reports and very sorry for the trouble.

A quick workaround would be, if possible, to simply disable rich logging with the environment variable CEEDLING_DECORATORS. This prevents emojis in logging and uses ASCII characters in place of fancier Unicode.

The VS Code extension is very definitely brittle and out of date. A sizable update for it is in the works. I am sorry it is not working well for you. First priority is Ceedling itself. Focus has been on supporting 1.1.0 and the forthcoming 1.2.0 that adds the most frequently requested features.

The VS Code extension was started elsewhere by a very generous community member and then handed off. We will be resuming work on it very soon. Please understand that the VS Code extension as is today is rather simplistic, has no self-tests of any kind, and is presently incapable of supporting much of what Ceedling does. It is in need of a great deal of work. We will get back to it very soon. Thank you for the PRs, etc.

[jake-kim-sndk]

@mkarlesky Thanks for your quick response.
I understand the importance of prioritization. Still, I also wanted to emphasize the importance of backward compatibility.
The workaround CEEDLING_DECORATORS=0 doesn't work at all, as it uses *, instead of the long-standing list marker - which was used in Ceedling before the revamp.
ThrowTheSwitch/Ceedling@be3e216#diff-0e6c20ddb1c6dbea12ba7f1ef770a3086e857d5c10269e64904dc1b9ddee9f11R42
I would've been better if this was considered during the Ceedling revamp, although it is a tiny thing and nobody would have noticed that vscode extension was parsing lists based on - unless someone was willing to dig into this codebase.

[mkarlesky]

@jake-kim-sndk I realized after my message that my workaround does not fix the issue. I apologize for the mistake.

And, yes, ideally all the projects could and would be updated together avoiding incompatibility. I hope you can appreciate that freely available tools created almost entirely through volunteer contributions generally cannot meet the expectations of commercial tools in terms of support and release planning. One way to help is for users and especially companies that rely on these tools to become GitHub sponsors and paying customers as we slowly make paid options available.

The next release of the VS Code extension will be happening in the next day or so. It has been nearly entirely rewritten now since taking it over. That process corrected the problem you reported and all other open issues.

[mkarlesky]

Version 2.0.0 of the extension was just published minutes ago. With all of the inner reworking, it was too big of a challenge to merge this PR. Many apologies on how long this work took and for closing this PR instead of providing proper credit. With a new revamped code base it should now be much easier to merge PR, rely on test coverage, etc.