Project

General

Profile

Actions

Task #90667

closed

Directory names for TSconfig not consistent and also not consistent in docs (CGL, T3 Explained)

Added by Sybille Peters over 4 years ago. Updated 12 days ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Code Cleanup
Target version:
-
Start date:
2020-03-06
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
10
PHP Version:
Tags:
Terminology
Complexity:
Sprint Focus:

Description

backend/Configuration/TSconfig
felogin/Configuration/TsConfig
form/Configuration/PageTS
frontend/Configuration/TSconfig
linkvalidator/Configuration/TsConfig

It's sometimes TSconfig or TsConfig.

And it's sometimes Page in TsConfig or PageTS.

Issue was raised in docs where it is also inconsistent:

https://github.com/TYPO3-Documentation/TYPO3CMS-Reference-CoreApi/issues/794

I don't know which way should be the "correct" way.

I found the discussion in decisions which is usually used to decide these things:

But the final post with the results does not mention the folder structure:


Related issues 1 (1 open0 closed)

Related to TYPO3 Core - Task #95822: General glossary for term definitions + workflow for introducing / improving termsAcceptedGarvin Hicking2021-10-30

Actions
Actions #1

Updated by Markus Klein over 3 years ago

  • Description updated (diff)
Actions #2

Updated by Markus Klein over 3 years ago

  • Description updated (diff)
Actions #3

Updated by Markus Klein over 3 years ago

Configuration/TsConfig/Page/
and
Configuration/TsConfig/User/

is the way to go IMO.

Actions #4

Updated by Sybille Peters over 3 years ago

See also merged patch: Unify spelling for TSconfig

Actions #5

Updated by Markus Klein over 3 years ago

That doesn't make the decision easier, does it?

But a completely different approach would be to rename TSconfig to what it actually is: BackendConfig

So what do you think Sybille? What's your proposal for Txxonfig?

Actions #6

Updated by Sybille Peters over 3 years ago

I haven't looked at this for a while so can't say off the top of my head.

But a completely different approach would be to rename TSconfig to what it actually is: BackendConfig

See also decision: https://decisions.typo3.org/t/clarification-of-term-typoscript/560/7?u=sypets

There was a suggestion to rename TSconfig to PageConfig and UserConfig.

Now you are suggestion BackendConfig. I think it is good to have the word Backend in there. But there is also other backend config, such as extensions configuration, $GLOBALS['TYPO3_CONF_VARS']['BE'], etc..

How about, "Backend Page Config" and "Backend User Config"

but these terms are too generic. I think it is good to have something like Flexforms which is very specific.

or "Page BackendTSconfig" and "User BackendTSconfig" - too long.

Also, I would differentiate between used in file / directory names and used in text (docs, BE GUI), so it might be

  • "Page BackendTSconfig"
  • and Configuration/BackendTSconfig/Page

I think this needs some tweaking.

There are 2 things to consider

1. What would be the best terms
2. Should we really change it because there will be lots of changes, confusion and collateral damage. (e.g. change translations, how do you even translate these things, add redirects in docs, rename files in core, change in docs) - God help us!

Actions #7

Updated by Sybille Peters over 3 years ago

Fun fact about naming of TSconfig:

Typescript uses the term "TSConfig", e.g. "TSConfig Reference" and tsconfig.json

https://www.typescriptlang.org/tsconfig

Actions #8

Updated by Markus Klein over 3 years ago

It's about time to rename TSconfig completely => BackendConfig

Actions #9

Updated by Sybille Peters 14 days ago

Update on this issue:

Current status:

It seems the issue is obsolete since page.tsconfig was introduced, unless tsconfig should be renamed. Not sure what convention there is for user tsconfig, though.

On renaming Tsconfig

There have been some suggestions to rename tsconfig in general. Changes like this are pretty extensive, so I am very hesitant about this. Already the file ending was renamed several versions back (from .typoscript to .tsconfig).

Also, the new file Configuration/page.tsconfig was introduced.

That would have been a good opportunity to make these kind of changes.

Actions #10

Updated by Garvin Hicking 14 days ago

  • Status changed from New to Needs Feedback

There's an effort/initiative to address terminology by Rachel and Tymoteusz, gathering all the terms TYPO3 has, to collectively think about possible renaming.

That list is currently in the works and I see you're also part of it (https://docs.google.com/spreadsheets/d/1qjCTsaGgifZAYhOV4Mtqall34h5Dyl5Z-1DzHBayBJU/).

Would you think we can close this issue here, and see what progress is made through that other effort?

Actions #11

Updated by Garvin Hicking 14 days ago

  • Related to Task #95822: General glossary for term definitions + workflow for introducing / improving terms added
Actions #12

Updated by Garvin Hicking 14 days ago

  • Status changed from Needs Feedback to Closed

I've found #95822 which is IMO good to carry that terminology issue further, hope that's ok with you

Actions #13

Updated by Riccardo De Contardi 14 days ago

  • Tags set to Terminology
Actions #14

Updated by Sybille Peters 12 days ago

Garvin Hicking: Agreed. Thanks.

Actions

Also available in: Atom PDF