* feat: add content source maps service * chore: refactor to fp and async.pipe * chore: use header instead of query param * fix: ignore polymorphic relations * chore: add error handling * fix: arrays of relations and medias * enhancement(getstarted): show nested values in preview * fix: update highlights when the dom changes * fix: highlight dimensions after text update * fix: strip away invisible characters from dom * fix: don't encode slugs * fix: handle fields in single components * enhancement: add rawWithIndices to traverseEntity patj * fix: handle components and repeatable components * fix: strapi utils build * fix: dynamic zones * chore: use dots for array indices not brackets * fix: content source map base url fallback * chore: use URLSearchParams instead of URL * chore: refinements * test: fieldUtils testing * fix: traverse-entity doc * chore: add traverse-entity tests * feat: scroll element into view on focus * chore: make email clickable in dummy preview * fix: single and double click behavior * chore: use css hover instead of mouseenter * enhancement: double click to edit notification * fix: display translated errors * fix: unit test * fix: null blocks value * enhancement: filter attributes in nested fields * fix: prevent losing iframe pointer events after closing popover
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.