Andrew Koebbe

@Sogl I just tried this out in the `devlop` branch and it does work for me. I was using the format of `04/01/2010` (mm/dd/yyyy). Can you see if changing your...

So are you saying you're using `dd/mm/yyyy`? Your "Wrong" situation seems like it's sorting `mm/dd/yyyy`. Is that correct?

Ok. I see what you're saying. Here is a more clear example... ```yaml #item 1 custom_date: '01/01/2010' #item 2 custom_date: '03/01/2010' #item 3 custom_date: '02/01/2020' #item 4 custom_date: '04/01/2019' ```...

I also wonder if it would be reasonable to pull a blueprint field definition in to know how to cast the value... OR add a property `value_type` to the `order`...

I just did some testing and ISO 9601 formatted dates work with both sorting and range limits using the dates my last example above.

I'm open to hearing what other devs think about either option I mentioned above for a real solution. Perhaps there are other options?

@mahagr could we not tap into the blueprint to inform sorting?

Thanks @danniehansen! I'm not actually sure what exactly the `getFormatCountInBuffer` returns. I only copied down what was in the ZPL docs (which have a lack of verbosity for this response)....

I've created a PR for this feature. The client now has a `getPrinterStatus` method that will return a developer friendly class to see the status and settings of the printer.

This seems like an ok workaround, I just don't like that each transformer has to have knowledge of the related transformer's `defaultIncludes` values.