Lars Nyström

Summer vacation is over, so I guess it's time to answer here :) Rails has the advantage of controlling the entire application stack and can therefore deal with timezone conversions...

I would prefer that. I think it's nice to provide sane defaults where the developer omitted them. The idea is to create the equivalent schemas on all different dbms if...

Here's what the footer says:

So, I added breakpoints on a few different `preventDefault()` calls using the Firefox debugger, and the one that is triggered when I do Cmd + 1 is a `callback` in...

`rel="noopener"` is not supported in Edge, IE11 or older versions of Firefox. It would be better to use `rel="noopener noreferrer"`, in order to solve this security issue for more browsers....

The workaround for this is to use `Zend\Db\Sql\Sql::buildSqlString()` instead of `Zend\Db\Sql\Select::getSqlString()`. Example: ``` // $adapter is a Zend\Db\Adapter\AdapterInterface // $select is a Zend\Db\Sql\Select $sqlObject = new Zend\Db\Sql\Sql($adapter); $sqlString = $sqlObject->buildSqlString($select,...

I haven't tried running this yet, but I like the idea. Why must "the flag setRequired" be set when adding the validator manually? Wouldn't it be better to just deprecate...

Hmm, yeah that's true. Do you think it would be possible to use the $data array as $context instead of the raw values? That would enable the Required-validator to check...

The problem is that they're initialized to null. Null is still a value, and would pass the required-validator. So we need the original input data, where the the input is...

Yes, that's why the input's name must be injected into the validator. If you add a `RequiredValidator::setName()` method, it will be compatible with the plugin manager.