Currently, only nucleotide and aminoacide data types are supported by the FastaImporter, and only if according to a heuristic (based on file extensions) the sequences are deemed to be ambiguous.
Packages can define their own datatype, and it would be convenient to import alignments with non-standard data types, that could pop up in the drop-down list.
A sanity check needs to be included to prevent nonsensical datatypes to be proposed (e.g. Binary for a nucleotide sequence), perhaps based on the set of characters in sequences and the code map of the data types.
Currently, only nucleotide and aminoacide data types are supported by the FastaImporter, and only if according to a heuristic (based on file extensions) the sequences are deemed to be ambiguous.
Packages can define their own datatype, and it would be convenient to import alignments with non-standard data types, that could pop up in the drop-down list.
A sanity check needs to be included to prevent nonsensical datatypes to be proposed (e.g. Binary for a nucleotide sequence), perhaps based on the set of characters in sequences and the code map of the data types.