basename truncates file extension, contains no path info

[mikaelkaron]

I'm not sure I understand how basename should be expected to work.

For example assuming this structure:

root/
root/dir/foo/one.md
root/dir/bar/two.md

CWD is root and I run:

user@shell:~/root$ m2j dir/*/*.md

Results:

• basename does not contain .md
• basename has no path info

Expected:

• basename to contain .md
• Either basename (or somewhere else in the json) should have the root/dir/(foo|bar) path info

[barraponto]

Right now, basename lacks the extension and is used, mainly, as the key in the generated object.
This will probably break if we have both conflict.md and conflict.markdown as file inputs.
To fix that, I think we could use hashed absolute paths (unreadable, but don't give away too many details from user environment). Or just get rid of the keys altogether, turning it into an array.

[scottstanfield]

I like this idea of turning the output into an array b/c of possible conflicts. Will consider for next release. Now that I have my CI pipeline and tests working, will be easier to add support.