Fix unexpected return tag on non-functions

[HO-COOH]

Fix/Feature/Other

Fix

A dirty fix to #210

• Description of the fix

Check the special return cases regardless of the setting for including return types. If it is false and all the case index is -1, then the param array shall be empty, so it mapped to nothing. Otherwise set param to [""]. So it could be mapped to return, without the types included.

• Added unit test

I added this test to config.Test.ts.

NOTE:
All your test() calls seems to have wrong order, should be test(actual, expected), but you have test(expected, actual).
I was so confused at first.

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (master@dbcf5dc). Click here to learn what that means.
The diff coverage is 50.00%.

@@            Coverage Diff            @@
##             master     #214   +/-   ##
=========================================
  Coverage          ?   32.03%           
=========================================
  Files             ?       14           
  Lines             ?     1027           
  Branches          ?      188           
=========================================
  Hits              ?      329           
  Misses            ?      696           
  Partials          ?        2           

Impacted Files	Coverage Δ
src/Lang/Cpp/CppDocGen.ts	22.81% <50.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update dbcf5dc...2a69505. Read the comment docs.

[cschlosser]

Thank you for your contribution.
Could you please remove the package-lock.json.
Some tools get confused when there is a yarn lock file as well.

Regarding the order of arguments for assertions: This is probably due to the diff being backwards otherwise iirc.
I can take another look at it to see if this is something that has sneaked in.

[HO-COOH]

@cschlosser see this update

For the wrong test I talked about, this is what I see

[cschlosser]

You're totally right.
I don't know why but this seems to have changed.