Stefan Crnjaković

On one hand, I'm with @sergeyklay and @Jurigag on this one. `Phalcon\Validatation\Validator\Regex` is meant to perform Regex validation, not type checking and type validations. But on the other hand, let's...

Actually, this is more NFR as this is obviously due to the fact that all POST/GET values are strings, with the exception of array of course. What I propose we...

@niden Without getting into a discussion on why would one want empty strings in a database, I suppose there is a valid use case somewhere, I still think those cases...

Yeah, I don't mind that approach, I just advocate NULL being default and empty string optional. That makes more sense to me.

The way radio buttons work in Phalcon, as far as I got them, is: Form initialization ``` $this->add(new Radio('published')); ``` View ``` {{ form.render('published', ['value':'Y']) }} {{ form.render('published', ['value':'N']) }}...

Well, sort of. It is hacky when it comes to labels, whereas it is quite valid when it comes to the input itself. I do generally agree with you, but...

I've made these from 2.0 branch - I had to completely port Tag\Select since _optionsFromResultSet() and _optionsFromArray() are declared private. - I extendend Forms\Element\Select so it uses newly created Tag\Select...

@sergeyklay any chances this will be implemented before 4.0? Need any help?

I use Volt and I just pass `-L Swig` instead of Volt, the syntax is absolutely the same (regarding blocks and functions) so it works like a charm, plus contexts...

Failed to compile against nginx 1.13.8, whereas one that @LambArchie suggested compiled just fine. This repo is not maintained at all, should we contact nginx to update their module pages...