#95722Why does TYPO3 have a slug-helper?
Description
Hello Community,
this is just to have a general understanding of a pattern on TYPO3 code, which I do not really understand.
Since TYPO3 9 we have inhouse pretty-urls. For this, as usual these days, we have fortunately slug fields on the entities. Thank you for all this.
TYPO3 is a very mature system and it is comprehensible that we have some legacy codes here and there that look weird from today’s perspective.
Now looking at the slug-helper I kind of get lost, why these kind of code-styles are still introduced on TYPO3. The slug-helper cannot be that old and at the same time TYPO3 is now enforcing dependency injection with non-public services. Therefore accessing containers and GeneralUtility::makeInstance is advised not to be done.
Well with a Helper like this it will be quite hard to obey these conventions:
$slugHelper = GeneralUtility::makeInstance(
SlugHelper::class,
$tableName,
$slugFieldName,
$fieldConfig
);
$slugHelper->generate($hereSomeArray, int $pid);
...
This way constructor injection is very hard up to not possible imho. Also it is not very intuitive to use. Why do we introduce a slug-helper in this pattern?
Imo the right way to do this would be for instance something like this:
$slugService = new SlugService();
$slugService->getGenerator($table, $fieldName)->generateByUid(int $uid)
// or
$slugService->generate($table, $fieldname, $uid)
// or
$slugService->generate(SlugGenerateConfigurationObject)
// or
...
This is just one of many possible patterns, nevertheless this way we could
- use enforced constructor injection
- dismiss usage of general utitlity
- write tests easily by simple injection instead of registering instances on containers, …
- understand usage simply by auto-complete
I have that feeling, that there should be some code patterns which are enforced on TYPO3 Core Code. I have this feeling, that in 5 years there will be a strong dependency on this slug-helper and there will be soon a lot of work to deprecate them.
Nevertheless I don’t see exactly what kind of recommended common pattern the current implementation is following.
Please correct me with literature if I am wrong and this pattern has some advantages.
Thank you for all your great work.
Kind regards
Rozbeh Chiryai Sharahi
Reviews 1
History 362
Show 337 earlier messages
-
Benni Mack commented and changed status
NewClosed <span data-processor="relativetime" data-value="2021-11-03T20:21:20+00:00" > 11/03/21, 20:21 </span>Hey Rozbeh Chiryai Sharahi,
this is all my fault, I should not have created the feature in the first place.
I can come up with excuses why I build it this in 2019 way – simply put I took the liberty of making it work “somehow” instead of coming up with a pattern due to time constraints. But now I know better and would build it differently – using all the concepts by the book. Now we have to stick with this code until someone will come up with a better alternative.
If you find the time, I’m more than happy if you can improve the concepts in this area.
I hope this answers your initial question. If you have any further questions, feel free to reach out to me directly at benni@typo3.org
All the best,
Benni. -
Gerrit Code Review pushed patch set 1 for main to change 74781 status
ClosedUnder Review <span data-processor="relativetime" data-value="2022-05-28T14:17:20+00:00" > 05/28/22, 14:17 </span> -
Gerrit Code Review pushed patch set 2 for main to change 74781 <span data-processor="relativetime" data-value="2022-05-28T14:47:25+00:00" > 05/28/22, 14:47 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 74781 <span data-processor="relativetime" data-value="2022-05-28T14:56:21+00:00" > 05/28/22, 14:56 </span>
-
Gerrit Code Review pushed patch set 4 for main to change 74781 <span data-processor="relativetime" data-value="2022-05-28T15:28:46+00:00" > 05/28/22, 15:28 </span>
-
Gerrit Code Review pushed patch set 5 for main to change 74781 <span data-processor="relativetime" data-value="2022-05-28T17:36:26+00:00" > 05/28/22, 17:36 </span>
-
Gerrit Code Review pushed patch set 6 for main to change 74781 <span data-processor="relativetime" data-value="2022-05-28T21:30:37+00:00" > 05/28/22, 21:30 </span>
-
Gerrit Code Review pushed patch set 7 for main to change 74781 <span data-processor="relativetime" data-value="2022-05-29T13:32:10+00:00" > 05/29/22, 13:32 </span>
-
Gerrit Code Review pushed patch set 8 for main to change 74781 <span data-processor="relativetime" data-value="2022-05-29T22:10:00+00:00" > 05/29/22, 22:10 </span>
-
Gerrit Code Review pushed patch set 9 for main to change 74781 <span data-processor="relativetime" data-value="2022-05-29T22:31:31+00:00" > 05/29/22, 22:31 </span>
-
Gerrit Code Review pushed patch set 10 for main to change 74781 <span data-processor="relativetime" data-value="2022-05-31T11:41:20+00:00" > 05/31/22, 11:41 </span>
-
Gerrit Code Review pushed patch set 11 for main to change 74781 <span data-processor="relativetime" data-value="2022-05-31T21:09:20+00:00" > 05/31/22, 21:09 </span>
-
Gerrit Code Review pushed patch set 12 for main to change 74781 <span data-processor="relativetime" data-value="2022-06-02T23:33:19+00:00" > 06/02/22, 23:33 </span>
-
Gerrit Code Review pushed patch set 13 for main to change 74781 <span data-processor="relativetime" data-value="2022-06-03T18:08:30+00:00" > 06/03/22, 18:08 </span>
-
Gerrit Code Review pushed patch set 14 for main to change 74781 <span data-processor="relativetime" data-value="2022-06-05T00:18:05+00:00" > 06/05/22, 00:18 </span>
-
Gerrit Code Review pushed patch set 15 for main to change 74781 <span data-processor="relativetime" data-value="2022-06-05T00:23:22+00:00" > 06/05/22, 00:23 </span>
-
Gerrit Code Review pushed patch set 16 for main to change 74781 <span data-processor="relativetime" data-value="2022-06-10T21:50:44+00:00" > 06/10/22, 21:50 </span>
-
Gerrit Code Review pushed patch set 17 for main to change 74781 <span data-processor="relativetime" data-value="2022-06-10T22:33:32+00:00" > 06/10/22, 22:33 </span>
-
Gerrit Code Review pushed patch set 18 for main to change 74781 <span data-processor="relativetime" data-value="2022-06-15T07:59:26+00:00" > 06/15/22, 07:59 </span>
-
Gerrit Code Review pushed patch set 19 for main to change 74781 <span data-processor="relativetime" data-value="2022-06-23T19:13:35+00:00" > 06/23/22, 19:13 </span>
-
Gerrit Code Review pushed patch set 20 for main to change 74781 <span data-processor="relativetime" data-value="2022-06-23T21:14:46+00:00" > 06/23/22, 21:14 </span>
-
Gerrit Code Review pushed patch set 21 for main to change 74781 <span data-processor="relativetime" data-value="2022-06-25T10:51:26+00:00" > 06/25/22, 10:51 </span>
-
Rozbeh Chiryai Sharahi commented and changed priority
Should haveCould have <span data-processor="relativetime" data-value="2022-06-25T11:13:37+00:00" > 06/25/22, 11:13 </span>Hello Benni Mack, Hello Oliver Hader,
Thank you for your replies to the topic. Late … but … I took the time to do my contribution.
Of course I learned that it was much much more work than expected, and looking at my initial message from today’s perspective … I was arrogant, not being aware of the amount of details considered behind a simple slug builder :D. I don’t want to imagine doing this with time constraints.
However, i pushed a possible approach and maybe it or some parts of it are useful.
Kind Regards
Rozbeh Chiryai Sharahi -
Gerrit Code Review pushed patch set 22 for main to change 74781 <span data-processor="relativetime" data-value="2022-06-25T15:13:30+00:00" > 06/25/22, 15:13 </span>
-
Gerrit Code Review pushed patch set 23 for main to change 74781 <span data-processor="relativetime" data-value="2022-06-26T16:41:21+00:00" > 06/26/22, 16:41 </span>
-
Gerrit Code Review pushed patch set 24 for main to change 74781 <span data-processor="relativetime" data-value="2022-06-26T18:22:54+00:00" > 06/26/22, 18:22 </span>
-
Gerrit Code Review pushed patch set 25 for main to change 74781 <span data-processor="relativetime" data-value="2022-06-26T22:04:06+00:00" > 06/26/22, 22:04 </span>
-
Gerrit Code Review pushed patch set 26 for main to change 74781 <span data-processor="relativetime" data-value="2022-06-27T11:23:41+00:00" > 06/27/22, 11:23 </span>
-
Gerrit Code Review pushed patch set 27 for main to change 74781 <span data-processor="relativetime" data-value="2022-06-27T15:09:54+00:00" > 06/27/22, 15:09 </span>
-
Gerrit Code Review pushed patch set 28 for main to change 74781 <span data-processor="relativetime" data-value="2022-06-27T16:07:28+00:00" > 06/27/22, 16:07 </span>
-
Gerrit Code Review pushed patch set 29 for main to change 74781 <span data-processor="relativetime" data-value="2022-06-27T22:42:11+00:00" > 06/27/22, 22:42 </span>
-
Gerrit Code Review pushed patch set 30 for main to change 74781 <span data-processor="relativetime" data-value="2022-06-29T18:25:39+00:00" > 06/29/22, 18:25 </span>
-
Gerrit Code Review pushed patch set 31 for main to change 74781 <span data-processor="relativetime" data-value="2022-06-29T23:08:44+00:00" > 06/29/22, 23:08 </span>
-
Gerrit Code Review pushed patch set 32 for main to change 74781 <span data-processor="relativetime" data-value="2022-07-01T13:08:42+00:00" > 07/01/22, 13:08 </span>
-
Gerrit Code Review pushed patch set 33 for main to change 74781 <span data-processor="relativetime" data-value="2022-07-04T22:06:28+00:00" > 07/04/22, 22:06 </span>
-
Gerrit Code Review pushed patch set 34 for main to change 74781 <span data-processor="relativetime" data-value="2022-07-04T22:23:21+00:00" > 07/04/22, 22:23 </span>
-
Gerrit Code Review pushed patch set 35 for main to change 74781 <span data-processor="relativetime" data-value="2022-07-05T22:09:39+00:00" > 07/05/22, 22:09 </span>
-
Gerrit Code Review pushed patch set 36 for main to change 74781 <span data-processor="relativetime" data-value="2023-07-06T15:46:30+00:00" > 07/06/23, 15:46 </span>
-
Gerrit Code Review pushed patch set 37 for main to change 74781 <span data-processor="relativetime" data-value="2024-04-10T17:02:12+00:00" > 04/10/24, 17:02 </span>
-
Gerrit Code Review pushed patch set 38 for main to change 74781 <span data-processor="relativetime" data-value="2024-04-12T10:43:36+00:00" > 04/12/24, 10:43 </span>
-
Gerrit Code Review pushed patch set 39 for main to change 74781 <span data-processor="relativetime" data-value="2024-04-12T12:51:13+00:00" > 04/12/24, 12:51 </span>
-
Gerrit Code Review pushed patch set 40 for main to change 74781 <span data-processor="relativetime" data-value="2024-04-12T14:11:44+00:00" > 04/12/24, 14:11 </span>
-
Gerrit Code Review pushed patch set 41 for main to change 74781 <span data-processor="relativetime" data-value="2024-04-12T21:05:50+00:00" > 04/12/24, 21:05 </span>
-
Gerrit Code Review pushed patch set 42 for main to change 74781 <span data-processor="relativetime" data-value="2024-04-12T21:09:37+00:00" > 04/12/24, 21:09 </span>
-
Gerrit Code Review pushed patch set 43 for main to change 74781 <span data-processor="relativetime" data-value="2024-04-12T21:21:18+00:00" > 04/12/24, 21:21 </span>
-
Gerrit Code Review pushed patch set 44 for main to change 74781 <span data-processor="relativetime" data-value="2024-04-13T09:14:47+00:00" > 04/13/24, 09:14 </span>
-
Gerrit Code Review pushed patch set 45 for main to change 74781 <span data-processor="relativetime" data-value="2024-04-13T09:36:41+00:00" > 04/13/24, 09:36 </span>
-
Gerrit Code Review pushed patch set 46 for main to change 74781 <span data-processor="relativetime" data-value="2024-04-13T09:41:52+00:00" > 04/13/24, 09:41 </span>
-
Gerrit Code Review pushed patch set 47 for main to change 74781 <span data-processor="relativetime" data-value="2024-04-13T10:36:24+00:00" > 04/13/24, 10:36 </span>
-
Gerrit Code Review pushed patch set 48 for main to change 74781 <span data-processor="relativetime" data-value="2024-04-13T10:45:51+00:00" > 04/13/24, 10:45 </span>
-
Gerrit Code Review pushed patch set 49 for main to change 74781 <span data-processor="relativetime" data-value="2024-04-13T16:55:18+00:00" > 04/13/24, 16:55 </span>
-
Gerrit Code Review pushed patch set 50 for main to change 74781 <span data-processor="relativetime" data-value="2024-04-14T08:32:18+00:00" > 04/14/24, 08:32 </span>
-
Gerrit Code Review pushed patch set 51 for main to change 74781 <span data-processor="relativetime" data-value="2024-04-16T21:55:07+00:00" > 04/16/24, 21:55 </span>
-
Gerrit Code Review pushed patch set 52 for main to change 74781 <span data-processor="relativetime" data-value="2024-04-17T05:21:01+00:00" > 04/17/24, 05:21 </span>
-
Gerrit Code Review pushed patch set 53 for main to change 74781 <span data-processor="relativetime" data-value="2024-04-17T05:38:15+00:00" > 04/17/24, 05:38 </span>
-
Gerrit Code Review pushed patch set 54 for main to change 74781 <span data-processor="relativetime" data-value="2024-04-17T05:41:56+00:00" > 04/17/24, 05:41 </span>
-
Gerrit Code Review pushed patch set 55 for main to change 74781 <span data-processor="relativetime" data-value="2024-04-17T19:09:00+00:00" > 04/17/24, 19:09 </span>
-
Gerrit Code Review pushed patch set 56 for main to change 74781 <span data-processor="relativetime" data-value="2024-04-17T22:12:48+00:00" > 04/17/24, 22:12 </span>
-
Gerrit Code Review pushed patch set 57 for main to change 74781 <span data-processor="relativetime" data-value="2024-04-17T22:24:35+00:00" > 04/17/24, 22:24 </span>
-
Gerrit Code Review pushed patch set 58 for main to change 74781 <span data-processor="relativetime" data-value="2024-04-17T22:32:51+00:00" > 04/17/24, 22:32 </span>
-
Gerrit Code Review pushed patch set 59 for main to change 74781 <span data-processor="relativetime" data-value="2024-04-17T22:39:24+00:00" > 04/17/24, 22:39 </span>
Rozbeh Chiryai Sharahi wrote:
> Nevertheless I don’t see exactly what kind of recommended common pattern the current implementation is following.
SlugHelperdoes not follow any pattern by the book. And (spoiler alert), that’s unfortunately not the only class in TYPO3 that mixes multiple patterns and approaches in one component – e.g. have a look intoDataHandler.So, please go ahead with implementing current
SlugHelperas statelessSlugServiceand I’ll happily look into it and review it.Personally I’d prefer
$slugService->generate(SlugGenerateConfiguration)as it seems to be as closed as possible, but still open and flexible to future changes in theSlugGenerateConfigurationDTO, e.g. adding additional properties.