The issue in the composer.lock file has been fixed (leftover from earlier merge conflicts), the branch has been rebased to the latest version of 11.x and the composer.lock file (hashes) has been updated.
This has been done with the help from Jess (@xjm), @stefdewa and Randy Fay.
More information on updating the composer.lock inside core can be found on
https://www.drupal.org/about/core/policies/core-dependency-policies-and-practices/managing-composer-updates-for-drupal-core →
.
I am starting to work on this issue.
I tested the change and the handler options ('reference method') are sorted alphabetically (case insensitive, on the label). I updated the issue summary with steps to reproduce the results.
Concerning the feedback in #24 🐛 EntityReferenceItem::fieldSettingsForm() should sort the $handlers_options Active : the target bundles are sorted alphabetically but case sensitive (using natsort() and not natcasesort()) in the DefaultSelection plugin.
I'm starting to work on this issue.
I was able to reproduce the issue as mentioned.
The easiest solution would be to add a cache clear at the end of the RecipeCommand. The question is if this is a sufficient solution. This might lead to unnecessary cache clears, e.g. when applying a recipe that would not require a cache clear or when adding multiple recipes at once.
The getting started documentation of distributions_recipes, also mentions that a cache clear is required after applying a recipe.
I will start looking into this issue in the mentored contribution room.
grietdk → created an issue.
grietdk → created an issue.
I've added an updated version of https://www.drupal.org/project/metatag/issues/2901039#comment-13147190 → allowing to index individual meta tags, that works with metag 2.0.x.
grietdk → made their first commit to this issue’s fork.
grietdk → created an issue.
grietdk → changed the visibility of the branch 8.x-4.x to hidden.
grietdk → changed the visibility of the branch 3418576-autocomplete-js to hidden.
grietdk → created an issue.