Thanks for the feedback!

Perhaps you could elaborate on your specific use-case and why you think a term listing is preferrable over using a (custom) post type?

I ask because we generally discourage folks from treating terms as content.

Supporting term listings would require major structural changes to FacetWP, and would likely add additional overhead.

Sure!

So currently I am developing a tractor website that lists a bunch of classic tractor data.

I have a Custom Post Type called "Tractor". This post type as 2 taxonomies attached to it, It has a "Manufacture" and "Era" taxonomy.

Let's say one of my users comes to my site, I have the A-Z alphabetical FacetWP for people to sort a list of all the Manufactures. I can't do this without being able to filter taxonomy terms.

Here is the test site I'm currently working on-

http://iron.imaginethismarketing.com/manufacturers/

If you head to that page you can see I have a list of Manufacture taxonomy terms but I have no way to filter this list with FacetWP

Apologies, but I've decided against this feature :\

Taxonomy terms shouldn't be treated as content itself, but rather as a means to categorize or describe other content.

Not only would this feature add complexity (and bloat) to the plugin, it honestly goes against data structure best practices.

WordPress was built around the concept of post types being the main content objects, with custom fields and taxonomies being the different approaches to enrich that content.