| # |
Aug 28th 2019, 14:24 |
 koeller |
:P |
| # |
Aug 28th 2019, 14:24 |
ricksaccous |
forever shall you use your IdeHelper powers for good and not evil |
| # |
Aug 28th 2019, 14:23 |
neon1024 |
It’s the modern way @admad |
| # |
Aug 28th 2019, 14:23 |
ricksaccous |
@koeller oh IdeHelper please aid us in our IDE usage, hint at the correct syntax |
| # |
Aug 28th 2019, 14:23 |
ricksaccous |
he can identify as both, there are no limitations |
| # |
Aug 28th 2019, 14:22 |
admad |
i thought he's Sebastian |
| # |
Aug 28th 2019, 14:21 |
ricksaccous |
you are indeed IdeHelper |
| # |
Aug 28th 2019, 14:20 |
koeller |
Ah ok, I see. Thank you. I’m IdeHelper |
| # |
Aug 28th 2019, 14:19 |
dereuromark |
Or you could easily make it added to https://github.com/dereuromark/cakephp-sandbox/blob/master/.phpstorm.meta.php/.ide-helper.meta.php#L147-L149 => that is if you use an ide that can understand such meta files. |
| # |
Aug 28th 2019, 14:15 |
dereuromark |
Also note that they become auto-discoverable and type-autocomplete for any find() call if you use IdeHelper to create IDE autocomplete file :slightly_smiling_face: |
| # |
Aug 28th 2019, 14:14 |
dereuromark |
I think he means the custom finders they can expose: https://github.com/dereuromark/cakephp-geo/blob/master/src/Model/Behavior/GeocoderBehavior.php#L57-L59 |
| # |
Aug 28th 2019, 14:14 |
ricksaccous |
that's a good example |
| # |
Aug 28th 2019, 14:14 |
ricksaccous |
yeah |
| # |
Aug 28th 2019, 14:13 |
koeller |
You talk about the GeocodeBehavior, @ricksaccous? |
| # |
Aug 28th 2019, 14:12 |
ricksaccous |
it's pretty neat |
| # |
Aug 28th 2019, 14:12 |
ricksaccous |
a geocoding behavior with a distance finder |
| # |
Aug 28th 2019, 14:12 |
ricksaccous |
i mean |
| # |
Aug 28th 2019, 14:12 |
ricksaccous |
yep just like in @dereuromarks Geocoding plugin he has a distance behavior |
| # |
Aug 28th 2019, 14:11 |
admad |
yes, put the custom finder in a behavior |
| # |
Aug 28th 2019, 14:11 |
koeller |
Hi all, is there a cake way to store the code of a custom finder in a file, like Model\MyCustomerFinder.php ? |
| # |
Aug 28th 2019, 13:45 |
ricksaccous |
sorry about that, lmao |
| # |
Aug 28th 2019, 13:45 |
ricksaccous |
i did enjoy that little goose chase of asking you to make it accessible though |
| # |
Aug 28th 2019, 13:45 |
ricksaccous |
@neon1024 i was going to suggest that next, glad you figured it out, lol |
| # |
Aug 28th 2019, 13:45 |
spriz |
I just realized that we run tests with debug => true, wouldn't you usually disable debug mode in tests/bootstrap.php? :P |
| # |
Aug 28th 2019, 13:18 |
dereuromark |
for tests you would usually overwrite in tests/bootstrap file then |
| # |
Aug 28th 2019, 13:18 |
dereuromark |
config app.php as documented for cache engine config |
| # |
Aug 28th 2019, 13:13 |
val |
@dereuromark do you know where is that done? |
| # |
Aug 28th 2019, 13:12 |
dereuromark |
basically making it always cache-invalidate |
| # |
Aug 28th 2019, 13:11 |
dereuromark |
this is what is done for debug mode pretty much anyway |
| # |
Aug 28th 2019, 13:11 |
dereuromark |
set the timeout to 1 or even 0 |
| # |
Aug 28th 2019, 13:11 |
val |
is there an easy way to disable one cache config? |
| # |
Aug 28th 2019, 13:10 |
admad |
except for the config name there is no differentiation between cache configs used by core and other user defined ones |
| # |
Aug 28th 2019, 13:07 |
val |
in 3.x |
| # |
Aug 28th 2019, 13:06 |
val |
Hi, is there an easy way to disable all caches except cake core in unit tests? |
| # |
Aug 28th 2019, 13:06 |
alexdd55976 |
it should be in the response after submitting the form |
| # |
Aug 28th 2019, 13:02 |
davorminchorov |
how would I display the validation errors? |
| # |
Aug 28th 2019, 13:01 |
javier.villanueva |
<?= dd($var) ?> |
| # |
Aug 28th 2019, 12:59 |
javier.villanueva |
without "echo" |
| # |
Aug 28th 2019, 12:58 |
javier.villanueva |
you can use dd in view too |
| # |
Aug 28th 2019, 12:35 |
alexdd55976 |
you do not wanna do it that way, i think |
| # |
Aug 28th 2019, 12:35 |
davorminchorov |
what I am trying to do is display validation errors under each field |