Issue #3496399: Add ability to skip starter recipe if it was preinstalled (!349) · Merge requests · project / drupal_cms · GitLab

Snippets Groups Projects

Merged Darren Oh requested to merge issue/drupal_cms-3496399:3496399-preinstall-starter-recipe into 1.x 4 months ago

Closes #3496399

Activity

Darren Oh added 2 commits 3 months ago
added 2 commits

088ca3f1 - 1 commit from branch project:1.x

e5501ce8 - Issue #3496399: Add ability to skip starter recipe if it was preinstalled

Compare with previous version
Darren Oh mentioned in merge request !348 (closed) 3 months ago

mentioned in merge request !348 (closed)
Darren Oh added 2 commits 3 months ago
added 2 commits

3c14be62 - 1 commit from branch project:1.x

15bb5e08 - Issue #3496399: Add ability to skip starter recipe if it was preinstalled

Compare with previous version
Darren Oh added 2 commits 3 months ago
added 2 commits

1dede5fe - 1 commit from branch project:1.x

fb6e8207 - Issue #3496399: Add ability to skip starter recipe if it was preinstalled

Compare with previous version
Darren Oh added 1 commit 3 months ago
added 1 commit

3c50c823 - Use Drupal state to reliably detect previously installed recipes

Compare with previous version
Darren Oh added 1 commit 3 months ago
added 1 commit

34aa1f82 - Remove unneeded code

Compare with previous version
Darren Oh added 1 commit 3 months ago
added 1 commit

96a6b670 - Remove unneeded use statement

Compare with previous version
Darren Oh added 1 commit 3 months ago
added 1 commit

be6deb85 - Issue #3496399: Add ability to skip previously installed recipes

Compare with previous version
Darren Oh added 1 commit 3 months ago
added 1 commit

46a37307 - Issue #3496399: Add ability to skip previously installed recipes

Compare with previous version
Darren Oh added 1 commit 3 months ago
added 1 commit

c92cbfc1 - Issue #3496399: Add ability to skip previously applied recipes

Compare with previous version
Darren Oh added 1 commit 3 months ago
added 1 commit

da50b025 - Issue #3496399: Add ability to skip previously applied recipes

Compare with previous version
Darren Oh @darrenoh 3 months ago

Author Contributor

I found that we can check the project_browser.applied_recipes state to determine what recipes were previously applied. As well as helping demo creators who deliberately apply recipes without completing installation, this helps users who accidentally interrupt the installer while it is applying recipes.
Darren Oh added 2 commits 3 months ago
added 2 commits

f0523767 - 1 commit from branch project:1.x

f080c59a - Issue #3496399: Add ability to skip previously applied recipes

Compare with previous version
Darren Oh added 5 commits 3 months ago
added 5 commits

f080c59a...35d8d171 - 3 commits from branch project:1.x

02ba87e8 - Issue #3496399: Add ability to skip previously applied recipes

4989bc4c - Add our own state key to track applied recipes

Compare with previous version
Darren Oh @darrenoh 3 months ago

Author Contributor

Updated to subscribe to the RecipeAppliedEvent and save state to our own key.
Adam G-H @phenaproxima started a thread on an old version of the diff 3 months ago

Resolved 3 months ago by Darren Oh
Last reply by Darren Oh 3 months ago

Darren Oh added 1 commit 3 months ago

added 1 commit

fc485d2e - Add our own state key to track applied recipes

Compare with previous version

Darren Oh added 2 commits 3 months ago

added 2 commits

8a4aee6d - Remove code that checks recipe parent directory
bde99b3a - Add delete applied recipes state to uninstall step

Compare with previous version

Adam G-H added 1 commit 3 months ago

added 1 commit

5104e3ad - Add documentation and test coverage

Compare with previous version

Adam G-H added 1 commit 3 months ago

added 1 commit

84ea4ca9 - Add documentation and test coverage

Compare with previous version

Please register or sign in to reply