Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add custom TSconfig to Content-Block #297

Open
robinson2 opened this issue Nov 19, 2024 · 1 comment
Open

Add custom TSconfig to Content-Block #297

robinson2 opened this issue Nov 19, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@robinson2
Copy link

In addition to the feature request "Add custom TypoScript to Content Block," which I find very valuable (especially regarding Data Processors), I would like to propose considering TSconfig at the same time.

I encountered a similar issue with the following requirement:

I am using …

basics:
  - TYPO3/Appearance

… in the config.yaml file and need to adjust the displayed layout options. It would be great if the following configuration could be handled directly within the element's directory:

TCEFORM.tt_content.layout {
  # remove layout options 1-3 from all FSC CTypes
  removeItems = 1,2,3
  types {
    my_element {
      altLabels {
        0 = 3-Columns
        1 = 2-Columns
        2 = Mixed
      }
      # change "removeItems" for this CType to re-allow options 1-2
      removeItems = 3
    }
  }
}

I can also imagine additional use cases that go beyond TCEFORM.tt_content (and data processors in the TypoScript case). For example, configuring a linkHandler for the element, which requires both TypoScript and TSconfig.

Therefore, it would likely be beneficial if both aspects—TSconfig and TypoScript—could be fully configurable via page.tsconfig and setup.typoscript files located directly in the element's directory.

@nhovratov nhovratov added the enhancement New feature or request label Nov 19, 2024
@nhovratov
Copy link
Contributor

Thanks for the feature request. We are aware of the desire to bundle everything you need including TypoScript and TSConfig into the Content Block. But this needs to go hand in hand with Site Sets, which allow scoping for sites. If we would introduce an own autoload feature for this, it would always be global. Hence, this is probably something for TYPO3 v14, where Content Blocks is an integral part of the Core and works together with Site Sets (Scoped Content Blocks per site).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants