Skip to content
Snippets Groups Projects
  1. Jun 12, 2024
  2. Jun 11, 2024
  3. Jun 10, 2024
  4. Jun 08, 2024
  5. Jun 07, 2024
  6. Jun 06, 2024
  7. Jun 05, 2024
  8. Jun 04, 2024
  9. Jun 03, 2024
    • Stefan Bürk's avatar
      [TASK] Introduce `YAML` file linting · 86f36638
      Stefan Bürk authored
      The `symfony/yaml` package provides the `yaml-lint`
      commandline tool to lint yaml files.
      
      This change introduces yaml file linting checks using
      the symfony tool, differencing `Services.yaml` from
      other yaml files.
      
      Resolves: #103931
      Releases: main, 12.4, 11.5
      Change-Id: I9442b38c439fb5f2d5507ca0ab70235b2dfd194a
      Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84481
      
      
      Tested-by: default avatarcore-ci <typo3@b13.com>
      Reviewed-by: default avatarStefan Bürk <stefan@buerk.tech>
      Tested-by: default avatarStefan Bürk <stefan@buerk.tech>
      86f36638
    • Imko Schumacher's avatar
      [BUGFIX] Fix initialization of 00:00 time input · 39b6e51b
      Imko Schumacher authored
      The value of the `time` input is sent as an ISO date to the
      FormEngine, except for the time "00:00", which is just submitted
      as "0".
      
      This has lead to the input field not getting populated by
      the JavaScript initialization, and the input "00:00" was lost.
      
      In cases where such a `time` input is set as a required
      field, the validation would then fail because of the field
      getting interpreted as being empty/unset.
      
      With this patch, a "0" value is also interpreted as a valid
      "1970-01-01T00:00:00+00:00" string, that is parseable by
      FormEngine. Note this only affects display within the
      FormEngine; the format of the stored data is not changed
      (converted by DataHandler to proper values and covered by
      existing tests).
      
      IMPORTANT: This only applies to NULLABLE time|timesec
      inputs. Only for this configuration it is possible to
      decide, that a stored "0" value in the database is
      actually "00:00" and not an unset entry.
      
      Integrators/developers need to set 'nullable'
      TCA key to 'true' of the corresponding 'config' array,
      in case they want to make a time/timesec input picker
      be able to store and retrieve "00:00" as a valid
      timestamp.
      
      Resolves: #102602
      Releases: main, 12.4
      Change-Id: Id5dae6564a5da9ab3abd99bdc14b718cc7064464
      Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84459
      
      
      Tested-by: default avatarBenjamin Franzke <ben@bnf.dev>
      Reviewed-by: default avatarBenjamin Franzke <ben@bnf.dev>
      Tested-by: default avatarcore-ci <typo3@b13.com>
      39b6e51b