Consider not adding trailing '/' to directory paths when generating CSV from JSON output

[johnmhoran]

While trying to match file/directory paths from one CSV to another, I've encountered challenges when some paths do, and others do not, include a trailing /.

I've examined the latest develop branch and it seems that while the JSON output of scancode-toolkit does not have a trailing / for directories, the CSV generated by scancode-toolkit (as part of a scan or via --from-json) adds a trailing / to each directory path. (I've downloaded/installed scancode-toolkit-21.2.25 on WSL2 but not yet had time to test the / in the CSVs.)

I don't think this is a bug -- it was probably incorporated for a specific purpose at some point -- but unless it's a breaking change of some sort, it would be helpful to remove that functionality from the CSV-generation process.

[mjherzog]

This was a feature in the past in order to visually distinguish between files without extensions and directories, but it is time to remove it because:

• The trailing "/" does not exist in any filesystem
• We have the Type field: F or D - to distinguish between files and directories
• There should not be any downstream impact because the CSV output is standalone - there are no SCTK functions to import or or otherwise perform further processing on a ScanCode file in CSV format

[shricodev]

@pombredanne @AyanSinhaMahapatra is this issue still open? I am planning to work on this issue but the --csv seems to be deprecated in even the v32.0.0rc1 pre-release version of scancode-toolkit.