Log message #4050391

# At Username Text
# Jul 11th 2017, 08:43 savant it would!
# Jul 11th 2017, 08:43 chris-andre But, seriously, have been thinking about it. But I honestly don't know if that would have been read much.
# Jul 11th 2017, 08:42 savant would be great if you started :slightly_smiling_face:
# Jul 11th 2017, 08:40 chris-andre No, I don't. I thought about "thecakenoobblog.com".
# Jul 11th 2017, 08:40 savant or you can use jekyll on github :slightly_smiling_face:
# Jul 11th 2017, 08:40 savant if not, its very easy to start one, wordpress.com provides hosting
# Jul 11th 2017, 08:40 savant if so, you can pay me back by blogging about that^
# Jul 11th 2017, 08:39 savant @chris-andre do you have a blog?
# Jul 11th 2017, 08:39 savant no problem
# Jul 11th 2017, 08:39 chris-andre Thanks.
# Jul 11th 2017, 08:39 chris-andre I'll go through and check that latest migrations is actually up and mark them up :slightly_smiling_face:
# Jul 11th 2017, 08:38 savant :)
# Jul 11th 2017, 08:38 chris-andre phinxlog is empty. And shame on me. Now I remember I truncated all tables to "re-seed" and start with a fresh db
# Jul 11th 2017, 08:36 chris-andre All migrations were up earlier. Then after the pull yesterday, it is showing down
# Jul 11th 2017, 08:36 savant i would check that
# Jul 11th 2017, 08:36 savant so did you maybe screw up the phinxlog table?
# Jul 11th 2017, 08:36 savant it does that comparison based on the database
# Jul 11th 2017, 08:35 chris-andre I usually check migrations status after every commit and every `migrations migrate`
# Jul 11th 2017, 08:35 chris-andre yes @savant . But tables exists
# Jul 11th 2017, 08:33 david_kim @neo21181 hi david
# Jul 11th 2017, 08:31 savant every migration is down?
# Jul 11th 2017, 08:30 chris-andre Hi. After committing changes in my beta-branch, I have pulled branch to prod. server (not first install). After this, migrations status shows that every migration is _down_. This have not happend before. Any idea?
# Jul 11th 2017, 08:24 heter @neon1024 i agree :-)
# Jul 11th 2017, 08:23 neon1024 @heter Well your own code doesn’t have to follow the core standards. I personally don’t like prefixing private/protected methods with an underscore, as it’s a PHP 4 convention. So I don’t do that in my own project code :slightly_smiling_face:
# Jul 11th 2017, 08:23 matt @cleptric thanks - i'll use patchEntity
# Jul 11th 2017, 08:21 cleptric And to go further, `newEntity` with passed data and `patchEntity` call the validation
# Jul 11th 2017, 08:21 heter ye i think overall the accessor one is more preferable by most of people, i just found that this kind of "pattern" is nice for me personally and i did use it on my projects aswell, but when some new developers were looking at my code they were often confused and asked why i didnt follow the global standard
# Jul 11th 2017, 08:20 savant just always use `__call` done
# Jul 11th 2017, 08:20 cleptric Chnage the data you pass to patchEntity
# Jul 11th 2017, 08:20 cleptric @matt ThaT#s the actually behavior
# Jul 11th 2017, 08:20 neon1024 They’re less confusing :slightly_smiling_face:
# 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?