unhelpful warnings during cobalt convert-jekyll

[kevinw]

At the very least, these warnings should probably have filenames and line numbers:

>cobalt convert-jekyll --source Docs --destination DocsCobalt
[warn]   unsupported file extension
[warn]   sub directory parsing is not supported yet
[warn]   unsupported file extension
[warn]   unsupported file extension
[warn]   unsupported file extension
[warn]   unsupported file extension
[warn]   unsupported file extension
[warn]   unsupported file extension
[warn]   sub directory parsing is not supported yet
[warn]   sub directory parsing is not supported yet
[warn]   unsupported file extension
[warn]   unsupported file extension
[warn]   unsupported file extension
[warn]   sub directory parsing is not supported yet
[warn]   sub directory parsing is not supported yet
[warn]   sub directory parsing is not supported yet
[warn]   sub directory parsing is not supported yet

[epage]

There is a lot more we need to do for jekyll support (see #276) but yeah, these warnings really do not help people figure out how to act on them.

[epage]

@Geobert can probably speak more to it, but what is probably going on

• unsupported file extension: The conversion is only prcoessing template files and not assets
• sub directory parsing is not supported yet: The conversion only supports processing a single directory, so its warning about skipped sub-directories.

We want to improve both of those. They are covered in the above referenced issue. Hope this helps to allow you to at least make progress for now.

[Geobert]

Yeah sorry about this feature, it was my first contribution on the project and it's a code I'm not really proud of. I'll try to add more details on these warnings but @epage is right: only md files are supported and only on one level of directory.

Event today, this feature is not really helpfull: the layout field does not complete with .liquid for instance, producing unusable files by cobalt.
And many more stuff I think…

@epage: assign this one to me please :)