Bugs Fixing
-
Fork
Make your fork of t3api on github https://github.com/sourcebroker/t3api
-
Clone
Clone your forked repo locally.
-
First run of ddev
Go inside cloned repo and run:
ddev restart
-
Install and make init test
Inside cloned repo run:
ddev ci 12
This will install project locally (for TYPO3 12) and make tests to check if your installed version is working well before you start to modify it.
-
Branch
Create branch in your repo.
-
Fix bug
When you modify code of t3api then a symlinked version at
.test/
is also modified and you can access your modified version of t3api at fully working TYPO3[T3_ VERSION]/ src/ t3api https://
[T3_ VERSION]. t3api. ddev. site Open https://t3api.ddev.site to get overview on user/password to backend.
Look at
.test/
. Except[T3_ VERSION]/ src/ t3api
you have there two extensions that can be helpful for testing.- First extension is
site
, which is regular TYPO3 local mods extension. -
Second extension is
t3apinews
, which is extension that expose extensionnews
models and is supposed to have only mods for news. To test it open:
Sometimes you may want to flush cache for the TYPO3 located at
.test/
. Of course you can do[T3_ VERSION]/ ddev exec "cd .
. But you can also use special ddev commandtest/ [T3_ VERSION] && ./ vendor/ bin/ typo3 cache: flush" ddev cache-
flush - First extension is
-
Documentation
Run
ddev docs
to run documentation in watch mode. Browser should open automatically. You can modify files atDocumentation
and watch in real time how the docs will looks like. Look at https://docs.typo3.org/m/typo3/docs-how-to-document/main/en-us/Index.html for info about formatting possibilities. -
Automated fixes and tests
If you think you are ready with your bug then:
- run automated fixes:
ddev fix
- run automated test on current TYPO3:
ddev ci
If all is ok then you can run full matrix test as it will be done on github.
ddev ci all
- run automated fixes:
-
Commit, push and make PR