Project

General

Profile

Actions
Copy link

Epic #96997

open

Add more types for TCA columns

Added by Benni Mack about 2 years ago. Updated about 2 years ago.

Status:
Accepted
Priority:
Should have
Assignee:
-
Category:
System/Bootstrap/Configuration
Target version:
-
Start date:
2022-02-21
Due date:
% Done:

90%

Estimated time:
(Total: 0.00 h)
Sprint Focus:

Description

We should add more TCA types for columns:

  • type=email
  • type=number
  • type=link
  • type=password (hashing algorithms need to be defined there)
  • type=date (dbType needs to be applied only there)
  • type=time (dbType needs to be applied only there)
  • type=datetime (dbType needs to be applied only there)
  • type=folder
Then later:
  • type=asset/file
  • type=richtext
  • look at the "relations" (inline,group,select) and how to unify this

This will drastically reduce the logic for integrators to write TCA and makes it easier in Core code to distinguish between the types (e.g. FormEngine and DataHandler).

Let's then see what is left of the "eval" list and all options can be streamlined.

I suggest to drop "eval" = domainName.

Subtasks 11 (1 open — 10 closed)

Task #96983: Separate internal_type=folder into own typeClosed2022-02-21

Actions
Feature #97013: Introduce "email" typeClosed2022-02-23

Actions
Task #97035: Use `required` in TCA in favor of eval listsClosed2022-02-25

Actions
Feature #97104: Introduce "password" typeClosedTorben Hansen2022-03-04

Actions
Feature #97159: Introduce TCA type "link"ClosedOliver Bartsch2022-03-09

Actions
Task #97193: Introduce TCA type="number"ClosedNikita Hovratov2022-03-16

Actions
Feature #97232: Introduce TCA type="datetime"ClosedOliver Bartsch2022-03-23

Actions
Feature #97271: New TCA type "color"ClosedOliver Bartsch2022-03-31

Actions
Task #97304: Unify new FormEngine element classesClosedOliver Bartsch2022-04-05

Actions
Task #97384: Use TCA option "nullable" instead of eval=nullClosed2022-04-14

Actions
Feature #97459: Register custom field evaluations via DIUnder Review2022-04-23

Actions
Actions
Copy link
 #1

Updated by Benjamin Kott about 2 years ago

Please consider:

- type=url
- type=telephone
- type=color
- type=currency
- type=toggle
- type=percent
- type=locale
- type=money
- type=range
- type=week
- type=code

Actions
Copy link
 #2

Updated by Georg Ringer about 2 years ago

  • Status changed from New to Accepted
Actions
Copy link
 #3

Updated by Benni Mack about 2 years ago

Benjamin Kott wrote in #note-1:

Please consider:

- type=url

ACK

- type=telephone

How to validate?

- type=color

ACK

- type=currency

How to deal with "." and separators and what should be different here to normal "double" evals?

- type=toggle

Can you explain this?

- type=percent

Is this number min=0 and max=100?

- type=locale

How should this look like?

- type=money

What is this?

- type=range

Can you give an example?

- type=week

Is this a number between 1 - 53?

- type=code

Can you explain this?

Actions
Copy link

Also available in: Atom PDF