Currently, using the API and registry in tandem, you still have to choose which extractor to run.
This PR implements the associated_file_extensions field for FileType, which can be used to provide the initial hint of which extractor to run. This should be used carefully, and extractors should fail gracefully when run on types they do not understand.
Related to #45, and takes ideas from #9.
This would exclude the case of e.g., POSCAR where the "file extension" is the whole filename, so could add some wording to that effect too
Next related fields would come from #9, where file patterns can be used to improve the matching, but this then becomes more complicated.
Currently, using the API and registry in tandem, you still have to choose which extractor to run.
This PR implements the
associated_file_extensionsfield forFileType, which can be used to provide the initial hint of which extractor to run. This should be used carefully, and extractors should fail gracefully when run on types they do not understand.Related to #45, and takes ideas from #9.