| # |
May 28th 2017, 15:08 |
 birdy247 |
www.mydomain.com/:sectionname/:id-:slug |
| # |
May 28th 2017, 15:02 |
birdy247 |
i.e. "portfolio" |
| # |
May 28th 2017, 15:02 |
birdy247 |
where "blog" is dynamic |
| # |
May 28th 2017, 15:02 |
birdy247 |
would connect to Articles::view |
| # |
May 28th 2017, 15:01 |
birdy247 |
i.e. www.mydoamin.com/blog/id:-:slug |
| # |
May 28th 2017, 15:01 |
birdy247 |
Is there a way to create a route based on a variable |
| # |
May 28th 2017, 14:05 |
inoas |
okay |
| # |
May 28th 2017, 14:05 |
inoas |
I really hope that 4.x will have non static time objects/configuration/setup |
| # |
May 28th 2017, 14:05 |
jeremyharris |
I don't try to avoid them necessarily, just use them judiciously |
| # |
May 28th 2017, 14:05 |
inoas |
it pretty much feels like programming with globals |
| # |
May 28th 2017, 14:04 |
inoas |
that's my fear |
| # |
May 28th 2017, 14:04 |
jeremyharris |
I've worked on big apps that have complex events and it takes a long time to figure out what's going on |
| # |
May 28th 2017, 14:04 |
inoas |
I feel like they break the FrontController MVP/MVC pattern |
| # |
May 28th 2017, 14:04 |
inoas |
Do you try to avoid them if it is sane? |
| # |
May 28th 2017, 14:03 |
jeremyharris |
Events are nice but yes it can be tricky to debug. I use them |
| # |
May 28th 2017, 14:03 |
inoas |
30° C here |
| # |
May 28th 2017, 14:03 |
inoas |
:/ |
| # |
May 28th 2017, 14:03 |
inoas |
But this time I think I have no choice but to use events and cells for mini-applications embedded in content first cms |
| # |
May 28th 2017, 14:02 |
inoas |
"I just like to know exactly what's happening" ;-) |
| # |
May 28th 2017, 14:02 |
inoas |
Personally I love when I can easily trace where a software runs... |
| # |
May 28th 2017, 14:02 |
inoas |
What's your stance on event driven software then? |
| # |
May 28th 2017, 14:01 |
jeremyharris |
That's a good plan. I should probably check it out again, it's been a while |
| # |
May 28th 2017, 14:01 |
inoas |
it felt like too much obligations... when things are done I may see if I can gain much from using CRUD |
| # |
May 28th 2017, 14:01 |
inoas |
I am currently moving away/skipping crud for one thing that I could have crudified... |
| # |
May 28th 2017, 14:00 |
jeremyharris |
No crud either haha, good guess |
| # |
May 28th 2017, 14:00 |
jeremyharris |
Maybe. I just like to know exactly what's happening |
| # |
May 28th 2017, 14:00 |
inoas |
no CRUD for your either? |
| # |
May 28th 2017, 14:00 |
jeremyharris |
Yep |
| # |
May 28th 2017, 14:00 |
inoas |
maybe something meditative about it (no pun!) |
| # |
May 28th 2017, 13:59 |
inoas |
really? |
| # |
May 28th 2017, 13:59 |
jeremyharris |
I write them all out hehe |
| # |
May 28th 2017, 13:59 |
inoas |
;-) |
| # |
May 28th 2017, 13:59 |
jeremyharris |
Not for me :slightly_smiling_face: |
| # |
May 28th 2017, 13:59 |
inoas |
Form->inputs() is <3 for instance :) |
| # |
May 28th 2017, 13:58 |
inoas |
I agree that verbosity can help (even without using IDEs) but I also like DRY ;) |
| # |
May 28th 2017, 13:58 |
inoas |
well once the feature for the routes settles I will try to stab that... |
| # |
May 28th 2017, 13:57 |
jeremyharris |
@inoas yes I imagine so. It'll internally create the array route I'm guessing |
| # |
May 28th 2017, 13:52 |
inoas |
then there is no conflict with HtmlHelper::link |
| # |
May 28th 2017, 13:52 |
inoas |
aka $this->Html->a('All Articles', 'Blog.Articles::index') |
| # |
May 28th 2017, 13:51 |
inoas |
right? |
| # |
May 28th 2017, 13:51 |
inoas |
@jeremyharris now that there seems to be an agreement on this https://github.com/cakephp/cakephp/issues/10689#issuecomment-304440165 ... it should be rather easy (even in user-land-code) to add HtmlHelper::a('label', 'shortcode', $options) which would use the Router::url() to parse things like $routes->connect('/articles/:id', 'Blog.Articles::view') |