| # |
May 17th 2021, 09:30 |
 dereuromark |
I see. As said before best to use automated approach as much as possible, and add on top what is missing then. Or provide pr to also allow automating that. |
| # |
May 17th 2021, 08:45 |
kevinfrom |
Plugin `A` might have an `AHelper` used in a plugin `B` template |
| # |
May 17th 2021, 08:45 |
kevinfrom |
I agree - but the problem is that some Theme plugins have View helpers used in different places. The hope was to avoid creating a ThemeView in every time to type this |
| # |
May 17th 2021, 08:42 |
dereuromark |
Helpers should never be configured in the templates imo. Thats what the tool write into appview class for. |
| # |
May 17th 2021, 08:40 |
neon1024 |
PHP Storm :point_up: |
| # |
May 17th 2021, 08:39 |
slackebot |
<neon1024> |
| # |
May 17th 2021, 08:38 |
neon1024 |
Yes |
| # |
May 17th 2021, 08:38 |
kevinfrom |
But does your IDE suggest methods when writing `$this->HelperName` then? |
| # |
May 17th 2021, 08:36 |
neon1024 |
If you use @dereuromark IdeHelper plugin, it can generate all these for you automatically |
| # |
May 17th 2021, 08:36 |
neon1024 |
`@var \Example\HelperName $HelperName` |
| # |
May 17th 2021, 08:36 |
neon1024 |
@kevinfrom I tend to just use `$HelperName` |
| # |
May 17th 2021, 08:03 |
kevinfrom |
A techical question - in a template, is it possible to define that my AppView uses a Helper? My problem is, that I'm not able to update the AppView class. ```/**``` |
| # |
May 17th 2021, 06:20 |
paolo.bragagni |
2. Where can I modify the actions code build from bake? |
| # |
May 17th 2021, 06:19 |
paolo.bragagni |
1. How can I build a 'stand alone' theme that is independent from the application? I'd like that all my (future) applications will have my own actions. |
| # |
May 17th 2021, 06:18 |
paolo.bragagni |
Hi, I read here https://book.cakephp.org/bake/2/en/development.html#bake-events thet if I want to add new action to my theme, I had to modify my src/Application . It's true? |
| # |
May 15th 2021, 20:10 |
kevin.pfeifer |
yup, that was the issue ,:) |
| # |
May 15th 2021, 20:02 |
kevin.pfeifer |
need to update my bake template ,:) |
| # |
May 15th 2021, 20:01 |
kevin.pfeifer |
ah, it seems its related to https://github.com/cakephp/bake/releases/tag/2.5.0 |
| # |
May 15th 2021, 19:52 |
kevin.pfeifer |
did i miss something or since when does baking a model result in the accessibility array having `=> 1,` instead of `=> true` as a value for each accessible field? |
| # |
May 15th 2021, 19:39 |
kevin.pfeifer |
sure thats going to be a testing nightmare ,:) |
| # |
May 15th 2021, 19:36 |
ndm |
Good luck debugging that... or even testing... testing generated SQL in 3rd party code? Oh boy, the slightest change in output produced by the core and you're in maintenance hell :upside_down_face: |
| # |
May 15th 2021, 19:36 |
ndm |
And that might not even cause an error, but just give you totally wrong results. |
| # |
May 15th 2021, 19:32 |
slackebot |
conditions are moved from outer queries to inner queries :grimacing: |
| # |
May 15th 2021, 19:32 |
ndm |
Unfortunately when developing 3rd party code for CakePHP I can't solely rely on the framework doing the right thing, I must be sure that I'm using it in a way that it is actually able to do the right thing. The dialects transforming code for example can really hit you by surprise, transforming tuples for Sqlite and Sqlserver really tripped me recently, as it can cause references to aliases targeting the wrong queries when |
| # |
May 15th 2021, 19:24 |
kevin.pfeifer |
thats why we are all very grateful to our cakephp core overlords who figure those things out for us lower folks so we can use a framework which just works :bow: |
| # |
May 15th 2021, 18:50 |
slackebot |
that could slowly approach almost exponential territory, that's wild x) |
| # |
May 15th 2021, 18:50 |
ndm |
Soooo, CI for code that needs to support all DBMS (MySQL, MariaDB, Sqlite, Postgres, SQL Server) and their quirks, basically needs to run at least 4 (DB types) * 2 (min/max PHP version) * 2 (min/max CakePHP version) jobs, + 1 or 2 separate ones for SQL server (if we're not too cocky and want to make it 5*2*2), that would already be 16-18 jobs, and god forbid I'd want to test with intermediate PHP/CakePHP versions too, over time |
| # |
May 15th 2021, 15:41 |
martin |
Yes i did find that, changed it to false |
| # |
May 15th 2021, 15:41 |
martin |
but since the server env is also based on docker it is easier to also run local in the same docker container I think |
| # |
May 15th 2021, 15:41 |
slackebot |
<kevin.pfeifer> |
| # |
May 15th 2021, 15:40 |
martin |
oh let me try to disable that, hope that solves the issue :P |
| # |
May 15th 2021, 15:39 |
kevin.pfeifer |
inside the docker engine settings |
| # |
May 15th 2021, 15:38 |
kevin.pfeifer |
the only thing (related to performance) is the fact, that for some reason debug mode is default on for the MacOS client which drastically reduces performance |
| # |
May 15th 2021, 15:38 |
martin |
with my private project I don't have that issue. with normal command I don't have the issue that it does not see the changes |
| # |
May 15th 2021, 15:37 |
martin |
ah ok, we work at work with docker, but having problems that sometimes docker does not respond, for a minute or so |
| # |
May 15th 2021, 15:36 |
kevin.pfeifer |
I can only say that me and my co-workers discarded any development in docker since its just to error prone and finicky to work with. We switched to a more "native" setup running PHP, MySQL etc. on the OS directly. Could be that its a docker problem, could be that there is some config needed or there is a bug somewhere, don't know :man-shrugging: |
| # |
May 15th 2021, 15:27 |
martin |
hmm seems to be working now after restarting docker-container+redis, how is the job cached by the worker? :P |
| # |
May 15th 2021, 14:46 |
martin |
hmmm maybe that was the problem, going to test my job again |
| # |
May 15th 2021, 14:42 |
martin |
even when I restarted the worker |
| # |
May 15th 2021, 14:41 |
martin |
hmm when I update a job, it still runs the old job? |
| # |
May 15th 2021, 14:38 |
admad |
Take the trouble of reading through the issue and the related PR. |