Skip to content
This repository has been archived by the owner on Nov 19, 2024. It is now read-only.

Commit

Permalink
Clarify TCEFORM structure (#556)
Browse files Browse the repository at this point in the history
While reading the documentation for the first time, we noticed that
it might be easier to understand if it is the same structure.

Co-authored-by: Davin Thiemann <[email protected]>
  • Loading branch information
github-actions[bot] and davinthiemann authored Nov 1, 2024
1 parent d49bd5e commit c8b8618
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion Documentation/PageTsconfig/TceForm.rst
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ apply. In general, a more specific property path overrides a less specific one:
Some properties apply to single fields, those can be usually set per table or
per table and record type. This leads to the property paths
`TCEFORM.[tableName].[fieldName].[propertyName]` to configure the field for all types
and `TCEFORM.[tableName].[fieldName].types.[typeName]` to configure a field for a specific
and `TCEFORM.[tableName].[fieldName].types.[typeName].[propertyName]` to configure a field for a specific
type, see the :ref:`TCA type section <t3tca:types>` for details on types.

While all that property path munging looks messy at first, it should become more
Expand Down

0 comments on commit c8b8618

Please sign in to comment.