3e666b1ad9
* feat(content-manager): contional fields * fix: remove logs * fix: skip validation incase field has condition invisible * chore: adding example * chore: merge develop * fix: filter out invisble fields * test: add e2e tests * fix: ensure that hidden fields are not validate or passed through at any point * feat: add support for components and dz * fix: saving relations on the fly * fix: skipping test * fix: dependencies * feat: add support for Dynamic Zone * fix: e2e tests * feat(CTB): conditional fields (#23662) * wip * wip need to fix schema * delete condition * clean up * feat: update condition form and related components, clean up logs, fix frontend * fix: only add to the first section * feat: add confirmation dialog and fixed UI * chore: remove unused code * chore: linting * fix: display related filed names in warning dialog --------- Co-authored-by: Bassel Kanso <bassel.kanso@strapi.io> * fix: skip displaying hidden dynamic zone in history * fix: ctb generate conditions for relation fields * feat: add tracker for conditional field count (#23828) * feat: add tracker for conditional field count --------- Co-authored-by: Ziyi <ziyi.yuan@strapi.io>
getstarted
This is an example app you can run to test your changes quickly.
Requirements
- Docker
- Docker compose
- Node
Installation
By default once you have setup the monorepo you will be able to run the getstarted app with a sqlite DB directly.
If you wish to run the getstarted app with another database you can use the docker-compose.dev.yml file at the root of the directory.
start the databases
Run the following command at the root of the monorepo
docker-compose -f docker-compose.dev.yml up -d
If you need to stop the running databases you can stop them with the following command:
docker-compose -f docker-compose.dev.yml stop
run the getstarted app with a specific database
DB={dbName} yarn develop
The way it works is that the getstarted app has a specific database.js config file that will use the DB environment variable to setup the right database connection. You can look at the code here
Warning
You might have some errors while connecting to the databases.
They might be coming from a conflict between a locally running database instance and the docker instance. To avoid the errors either shutdown your local database instance or change the ports in the ./config/database.js and the docker-compose.dev.yml file.