
* feat(releases): add release column to CM list view (#19926) * draft: bulk release injection zone added * chore: implement cm-api to strapi-app & description component renderer * feat: bulk delete action * Revert "draft: bulk release injection zone added" This reverts commit 2d9e8872e847327888d988009fa16f91b5f1c777. * feat: bulk unpublish action added * feat: default bulk publish action * fix: variable renaming * fix: on close of modal updated and refetched list on publish action completion * fix: removed IZ publish and unpublish modals, e2e tests added for default bulk actions * tests: e2e updated for publish button disabled state * fix: bug fixed on publishing with already published entries * fix: e2e tests * fix: reverted IZ components * feat: bulk release action added * update: check right permissions to show add to release button * update: bulk actions modal updated to accept content(modalbody+modalfooter), publish action and release actions updated accordingly * fix: types * test: bulk release e2e test added * fix: e2e test * fix: test case timeout added, notification component updated to not saved message * feat: inject release column in LV * fix: minor changes * fix: remove commented code * fix: upgraded styled components to fix the error: defaultProps circularly references * feat(content-releases): add to be released in column in list view * fix: types and 0 releases entry * fix: invalidate entries in release after bulk release or on deleting a release action * tests: e2e tests added for release column * tests: e2e updated to create new release and then add bulk release * fix: minor changes, test fixed * fix: delete release action invalite tag added back * fix: e2e test * apply josh feedback| --------- Co-authored-by: Josh <37798644+joshuaellis@users.noreply.github.com> Co-authored-by: Fernando Chavez <fernando.chavez@strapi.io> * chore(deps): revert sharp to 0.32.6 (#20066) * fix: fix boot issue when removing i18n from an app * chore: get i18n service outside the for loop * chore: remove empty spaces * v4.23.0 --------- Co-authored-by: Madhuri Sandbhor <madhurisandbhor@gmail.com> Co-authored-by: Josh <37798644+joshuaellis@users.noreply.github.com> Co-authored-by: Fernando Chavez <fernando.chavez@strapi.io> Co-authored-by: markkaylor <mark.kaylor@strapi.io> Co-authored-by: Alexandre BODIN <alexandrebodin@users.noreply.github.com>
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.