This project is mirrored from Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
Last successful update .
  1. 23 Apr, 2021 1 commit
    • Benjamin Franzke's avatar
      [TASK] Update to Lit v2-rc1 · d0da616d
      Benjamin Franzke authored
      Lit is the umbrella term for the next major
      lit-html (v2) and lit-element (v3) versions.
      Therefore we will refer to these components as
      *Lit* in TYPO3 from now on as well.
      These two libraries also have been migrated into
      a single entry point module named `lit`.
      It is officially described as:
      > The main module exports the core pieces needed for component
      > development: LitElement, html, css, and the most
      lit-html v2 and lit-element v3 are mostly compatible
      to the previous major versions. Main changes are
       * Deprecation of the `lit-element` entry point in
         favor of the new `lit` module
       * @internalProperty changed to @state
       * shadow css declaration via static property
         instead of static getter method
       * The CSSResult type declaration is gone
       * Directive (currently unused in TYPO3) API has changed
      Related testing framework change is:
      Commands used:
        rm -rf typo3/sysext/core/Resources/Public/JavaScript/Contrib/{@lit,lit-element,lit-html,lit}/
        yarn add lit@^2.0.0-rc.1 lit-html@^2.0.0-rc.2 lit-element@^3.0.0-rc.1
        yarn add --dev rollup@^2.32.0 @rollup/plugin-replace
        grunt build
        git add typo3/sysext/core/Resources/Public/JavaScript/Contrib/{@lit,lit-element,lit-html,lit}/
        composer require --dev typo3/testing-framework:^6.8.1
        composer require --dev typo3/testing-framework:^6.8.1 \
          --no-update --working-dir=typo3/sysext/core
      Resolves: #93965
      Releases: master
      Change-Id: I9b659d851e6ad9dc3cc649bd40aab886b86fb0f8
      Tested-by: Oliver Hader's avatarOliver Hader <>
      Tested-by: default avatarTYPO3com <>
      Tested-by: core-ci's avatarcore-ci <>
      Tested-by: Benni Mack's avatarBenni Mack <>
      Tested-by: Benjamin Franzke's avatarBenjamin Franzke <>
      Reviewed-by: Oliver Hader's avatarOliver Hader <>
      Reviewed-by: Benni Mack's avatarBenni Mack <>
      Reviewed-by: Benjamin Franzke's avatarBenjamin Franzke <>
  2. 11 Mar, 2021 1 commit
  3. 01 Mar, 2021 1 commit
  4. 16 Feb, 2021 1 commit
  5. 15 Feb, 2021 1 commit
  6. 08 Feb, 2021 2 commits
    • Benjamin Franzke's avatar
      [TASK] Drop unneeded renderElement from lit-helper · 8cbd504f
      Benjamin Franzke authored and Christian Kuhn's avatar Christian Kuhn committed
      renderElement() was added in patchset 2 of #93446.
      The code was then refactored to use renderHTML, but the method was
      forgotten to be removed in the final patchset.
      Now, the intention of the mentioned patchset 2 was to render nodes
      directly to the DOM in PageTreeDragHandler, instead of rendering to
      a temporary element, just to export and re-import as HTML string
      with jQuery/innerHTML.
      Therefore PageTreeDragHandler is now refactored to a new,
      (internal) method renderNodes() which allows the returned
      nodes to be directly attached to the document.
      Also, while at it, all other lit-helper methods are marked as
      internal as well, as they are still subject to change:
       * `renderHTML()` is only needed when mixing traditional jQuery
         rendering and lit-html (same as for the new `renderNodes()`.)
       * The `icon()` method could likely be replaced by a custom
         <typo3-backend-icon> component
       * `lll()` is only of use for globally available language identifiers
         (which are added via inline JS)  So this is also likely to change
         when more backend modules start to use lit-html/LitElement.
      Resolves: #93464
      Related: #93446
      Releases: master
      Change-Id: I61ab778e28e32b75b6e7965b75259beedbb10ae3
      Tested-by: default avatarTYPO3com <>
      Tested-by: core-ci's avatarcore-ci <>
      Tested-by: Benni Mack's avatarBenni Mack <>
      Tested-by: Christian Kuhn's avatarChristian Kuhn <>
      Reviewed-by: Benni Mack's avatarBenni Mack <>
      Reviewed-by: Christian Kuhn's avatarChristian Kuhn <>
    • Benni Mack's avatar
      [TASK] Clean up Drag&Drop Handling in PageTree · 85c7264b
      Benni Mack authored and Georg Ringer's avatar Georg Ringer committed
      The PageTree components for the navigation area consists of:
      * PageTreeElement (container for rendering the navigation area w. toolbar + dragdrop + tree)
      * PageTreeToolbar (uses DnD for creating new items)
      * PageTree (JS, subclass of SvgTree)
      * PageTreeDragDrop
      This patch aims to rework the "PageTreeDragDrop" javascript file
      by moving separate logic into separate classes (as much as possible)
      and into a more stable API, being a first part.
      PageTreeDragDrop is a mixed code class currently,
      and is now split up in various separate classes:
      * DragDropHandler (interface)
      * ToolbarDragHandler -> used as the Toolbar Draggable Handler for new pages
      * PageTreeNodeDragHandler => used for moving/copying and deleting existing pages/nodes
      * PageTreeDragDrop now acts as a simple wrapper for d3-drag but still has some shared state
      For Future Reference:
      It is still up to decide on how to further decouple the code.
      Idea 1: Putting the d3-drag initialization into the right
      place and avoiding cross-dependencies. In general "initializeDragForNode"
      would also be handled via events, and all options / settings would be
      moved into the PageTreeDragDrop class.
      Ideally the PageTreeDragDrop contains the status of the
      current drag+drop action (position, node etc), so the PageTree
      would not know of anything itself.
      Idea 2: Another possibility is to use the current "PageTreeDragDrop"
      as a generic "TreeDragDropManager" because it does not
      contain any Page-Tree specific code anymore, but could be carried
      on later-on.
      The current change is already a good step as it moves all code
      to TypeScript and minimizes injection via constructors (except
      for the Tree itself).
      Resolves: #93446
      Releases: master
      Change-Id: Ibd7a067c1e6a821b138a8cc2971ec8133392b600
      Tested-by: default avatarTYPO3com <>
      Tested-by: Andreas Fernandez's avatarAndreas Fernandez <>
      Tested-by: Georg Ringer's avatarGeorg Ringer <>
      Reviewed-by: Andreas Fernandez's avatarAndreas Fernandez <>
      Reviewed-by: Georg Ringer's avatarGeorg Ringer <>
  7. 29 Dec, 2020 1 commit
  8. 18 Dec, 2020 2 commits
  9. 13 Dec, 2020 1 commit
  10. 07 Sep, 2020 1 commit
  11. 07 Aug, 2020 1 commit
  12. 19 Apr, 2020 1 commit
  13. 17 Apr, 2020 1 commit
  14. 23 Mar, 2020 1 commit
  15. 02 Mar, 2020 1 commit
  16. 22 Feb, 2020 1 commit
  17. 03 Feb, 2020 1 commit
  18. 02 Feb, 2020 2 commits
  19. 25 Jan, 2020 1 commit
  20. 24 Jan, 2020 2 commits
  21. 20 Jan, 2020 1 commit
  22. 11 Dec, 2019 1 commit
  23. 06 Dec, 2019 1 commit
  24. 05 Apr, 2019 1 commit