Yurii Kuznietsov

I will add this request to the backlog. Not sure yet whether we will add it, need more time to think.

Just letting know that unlikely to be added in the nearest future. It's too much work as always. For those who need it, I recommend implementing a customization which is...

Hi, This raise some design issues. It was supposed that the Converter class is user agnostic. I'll consider this enhancement when get a chance, maybe will re-implement, not sure. To...

See https://github.com/espocrm/espocrm/blob/8.1.1/application/Espo/Core/Select/Where/ConverterFactory.php#L150. As an option, you can have this filters only for date view.

You can also by pass the date-time transformer and rely only on where item converter for both date-times and dates. I think this would be the easiest and future-proof.

This can be useful for extension developers. For those who develop only for a specific instance, it's not a necessity.

It seems it determines encoding here: https://github.com/laminas/laminas-mail/blob/2.25.1/src/Header/Subject.php#L105. As encoding set to UTF-8 it will encode the header. If we remove *setEncoding*, not sure if everything will work fine. We would...

 I think if we remove it, we might get problems. Maybe added *=?UTF-8?Q?* should not be considered as a problem? If it really may cause issues with spam detectors,...

Related: https://github.com/laminas/laminas-mail/issues/54

I tried w/o setEncoding and it failed to send when met UTF-8 characters in the From Name, requiring explicitly set UTF-8 for the 'from' header. This should be the same...