mirror of https://github.com/FriendsOfTYPO3/tea.git synced 2024-11-10 06:36:13 +01:00

Compare commits

..

No commits in common. "cd6df41eb7901cb2a30137a4028819eb1c958bc8" and "c68c72096c7e13ff8451383240eca309620f2523" have entirely different histories.

4 changed files with 7 additions and 70 deletions

View file

@ -102,7 +102,7 @@ jobs:
npm ci npm ci
- name: "Run command" - name: "Run command"
run: | run: |
npm run ci:lint:${{ matrix.command }} npm run lint:${{ matrix.command }}
unit-tests: unit-tests:
name: "Unit tests" name: "Unit tests"
runs-on: ubuntu-24.04 runs-on: ubuntu-24.04

View file

@ -2,10 +2,10 @@ javascript-lint:
extends: .default-frontend extends: .default-frontend
stage: lint stage: lint
script: script:
- npm run ci:lint:js - npm run lint:js
style-lint: style-lint:
extends: .default-frontend extends: .default-frontend
stage: lint stage: lint
script: script:
- npm run ci:lint:style - npm run lint:style

View file

@ -8,66 +8,3 @@ Development environment
You can run the code quality checks and automated tests locally (using a You can run the code quality checks and automated tests locally (using a
local PHP, Composer, and database) or using runTests.sh. local PHP, Composer, and database) or using runTests.sh.
To kickstart the project, we suggest the usage of the
`TYPO3-testing-distribution <https://github.com/oliverklee/TYPO3-testing-distribution/>`__
by Oliver Klee as development environment. The distribution comes with a frontend,
example data and predefined plugins.
.. index:: Clone TYPO3 Testing Distribution
.. code-block:: bash
git clone git@github.com:oliverklee/TYPO3-testing-distribution.git
Also clone the tea extension.
.. index:: Clone Tea Extension
.. code-block:: bash
git clone git@github.com:FriendsOfTYPO3/tea.git
You can organize the folder structure as you wish, but lets say your folder
structure looks like this:
.. index:: Folder structure
.. code-block:: bash
git\
TYPO3-testing-distribution
tea
Inside the testing distribution there is a file
:file:`docker-compose.extensions.yaml.template` which mounts the used extensions. This file need to be renamed and adjusted.
.. index:: Create docker-compose.extensions.yaml
.. code-block:: bash
cp .ddev/docker-compose.extensions.yaml.template .ddev/docker-compose.extensions.yaml
The file needs to mount the tea extension into the testing distribution. Keep in mind
that you use the correct paths here.
.. index:: Mount extension into testing distribution
.. code-block:: yaml
services:
web:
volumes:
- "$HOME/git/tea:/var/www/html/src/extensions/tea:cached,ro"
After that you can start the testing distribution using ddev.
.. index:: Start the testing distribution
.. code-block:: bash
ddev start
ddev composer install
ddev install-typo3
ddev db-import
After that you should be able to access the frontend:
.. code-block:: bash
ddev launch

View file

@ -14,10 +14,10 @@
"npm": "^10.5.0" "npm": "^10.5.0"
}, },
"scripts": { "scripts": {
"ci:lint:js": "eslint 'Resources/Public/**/*.js'", "lint:js": "eslint 'Resources/Public/**/*.js'",
"fix:lint:js": "eslint 'Resources/Public/**/*.js' --quiet --fix", "lint:js:fix": "eslint 'Resources/Public/**/*.js' --quiet --fix",
"ci:lint:style": "stylelint Resources/Public/**/*.css", "lint:style": "stylelint Resources/Public/**/*.css",
"fix:lint:style": "stylelint Resources/Public/**/*.css --fix" "lint:style:fix": "stylelint Resources/Public/**/*.css --fix"
}, },
"devDependencies": { "devDependencies": {
"eslint": "^9.2.0", "eslint": "^9.2.0",