[feature] Handle files in unknown languages

[ianlewis]

Handle text files in unknown languages using a generic configuration. This may be able to support files in languages that aren't explicitly known.

For example:

• Line comments start with # or //

[anatoly-scherbakov]

I was going to create a separate issue requesting GraphQL support, but this covers that.

[ianlewis]

I was going to create a separate issue requesting GraphQL support, but this covers that.

It might be good to have GraphQL specific support so that it could support documentation comments.

[ianlewis]

I was going to create a separate issue requesting GraphQL support, but this covers that.

BTW, do folks often keep GraphQL in files checked into a repo?

[anatoly-scherbakov]

@ianlewis yes, at least two use cases from the top of my head:

1. GraphQL schema files can be stored in a repo if the GraphQL framework in use is schema-first (like Ariadne for Python);
2. Tests covering a GraphQL API have GraphQL files with test requests chilling around them.

If GraphQL code is in a file contrary to being embedded, as an opaque string, into source code, — an IDE (having PyCharm in mind here) offers navigation and schema validation facilities for said code.

[ianlewis]

Right now todos will ignore files of an unknown type if run with a directory. This issue would likely cover files passed directly on the command line. Otherwise it might pick up files it shouldn't otherwise parse.

[ianlewis]

I was going to create a separate issue requesting GraphQL support, but this covers that.

@anatoly-scherbakov I added a separate issue for GraphQL support specifically on #1609