| # |
Jul 11th 2017, 08:20 |
 neon1024 |
I like accessor methods |
| # |
Jul 11th 2017, 08:20 |
cleptric |
I don’t like them personally, but we have quite a few core members that also like them :slightly_smiling_face: |
| # |
Jul 11th 2017, 08:19 |
cleptric |
Yeah, this mainly done do enable better type hinting |
| # |
Jul 11th 2017, 08:19 |
matt |
Good morning! I'm creating an entity using newEntity() then setting field values manually before saving it. That doesn't appear to be calling validationDefault on the table so no validation is occuring. Is there a way to force the validation check? Thanks |
| # |
Jul 11th 2017, 08:19 |
heter |
i really loved them :) |
| # |
Jul 11th 2017, 08:19 |
heter |
yep |
| # |
Jul 11th 2017, 08:19 |
cleptric |
A, mixed mode methods :slightly_smiling_face: |
| # |
Jul 11th 2017, 08:19 |
heter |
basically i meant - setters / getters change |
| # |
Jul 11th 2017, 08:19 |
heter |
well maybe i called it wrong |
| # |
Jul 11th 2017, 08:18 |
cleptric |
> coding-standards changes? |
| # |
Jul 11th 2017, 08:18 |
neon1024 |
CakePHP has had coding standards since 2.x |
| # |
Jul 11th 2017, 08:18 |
heter |
im sick and tired of these symfony only lovers which often are blind with all the standards and they can't think outstanding anymore and just follow standards which aren't always best |
| # |
Jul 11th 2017, 08:18 |
neon1024 |
I would argue that it already is. |
| # |
Jul 11th 2017, 08:17 |
heter |
never used it on big projects but i would love to |
| # |
Jul 11th 2017, 08:17 |
heter |
specially for medium sized projects |
| # |
Jul 11th 2017, 08:16 |
heter |
i really hope that after cake4 release with all these coding-standards changes people will finally find out that cakephp is really powerfull and developer friendly |
| # |
Jul 11th 2017, 08:13 |
david_kim |
simple cakephp better |
| # |
Jul 11th 2017, 08:13 |
david_kim |
laravel gave me complicated version dependency hell |
| # |
Jul 11th 2017, 08:02 |
savant |
@david_kim if you follow along with each minor 3.x release, you should be in great shape to upgrade to 4.x |
| # |
Jul 11th 2017, 08:00 |
heter |
thanks @savant if ill find some interesting weird problem ill let u know |
| # |
Jul 11th 2017, 08:00 |
heter |
yep makes sense |
| # |
Jul 11th 2017, 08:00 |
savant |
and write the code to send an email |
| # |
Jul 11th 2017, 08:00 |
savant |
then `include 'vendor/composer/autoload.php'` (or whatever) |
| # |
Jul 11th 2017, 07:59 |
savant |
you can certainly just `composer require cakephp/cakephp` |
| # |
Jul 11th 2017, 07:59 |
savant |
@heter we haven’t released it as standalone, but here it is: https://github.com/cakephp/cakephp/tree/master/src/Mailer |
| # |
Jul 11th 2017, 07:58 |
david_kim |
@savant ok i understand. |
| # |
Jul 11th 2017, 07:58 |
slackebot |
there's also some issue with cake mailer which is not handling some weird case |
| # |
Jul 11th 2017, 07:58 |
heter |
@savant continuation of email problem case - so ive downloaded official sendgrid library to try to prove hosting guys that something is wrong with server configuration - but with official library its working on both of servers - with cake its working on one of them and on second one its giving me error - is there somewhere the cakephp3 mailer as a outstanding library so i could prepare like one-file test with same configuration using cakephp3 m |
| # |
Jul 11th 2017, 07:58 |
savant |
Does that make sense, @david_kim ? |
| # |
Jul 11th 2017, 07:57 |
savant |
but those are *very* rare, and usually related to a severe security issue |
| # |
Jul 11th 2017, 07:57 |
savant |
note: there *are* a few cases where we need to remove an interface in a minor release |
| # |
Jul 11th 2017, 07:56 |
savant |
what is this, laravel? |
| # |
Jul 11th 2017, 07:56 |
savant |
so no, 3.8 is not a more suitable name |
| # |
Jul 11th 2017, 07:56 |
savant |
We can’t remove deprecated code in a minor release such as a 3.x because that would not follow semver |
| # |
Jul 11th 2017, 07:56 |
savant |
so if you’ve upgraded to remove all deprecated code usage and are running php 7.1, you are done |
| # |
Jul 11th 2017, 07:56 |
savant |
in 4.x, we remove all that dead code in the core |
| # |
Jul 11th 2017, 07:56 |
savant |
so you can just update your code |
| # |
Jul 11th 2017, 07:55 |
savant |
we will already have provided things you can replace it with - in fact, you can do that now for anything already deprecated |
| # |
Jul 11th 2017, 07:55 |
savant |
in 3.6, we’ll insert all those warnings, so if you run with error_reporting set high enough, those will appear during normal execution, logging, or tests |
| # |
Jul 11th 2017, 07:55 |
savant |
just not very many warnings are being raised in code |
| # |
Jul 11th 2017, 07:54 |
savant |
at the moment, we’ve already marked a lot of stuff as deprecated |