- Issue created by @acbramley
- 🇬🇧United Kingdom catch
+1, while the pattern works well, I think if you counted the number of people who know all the different bits of the pattern and why they're required, you'd not run out of toes, maybe even have some fingers left - config updates aren't needed that regularly and we had a lot of updates that failed to implement this properly in Drupal 8/9/10.
- 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
I think if you counted the number of people who know all the different bits of the pattern and why they're required, you'd not run out of toes, maybe even have some fingers left
🤣🤣🤣 👏
We should standardise these classes with an interface + base class to make them easier to implement and reduce boilerplate.
🤩
- 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
FYI: updated 📌 Improve the way to detect if the code component has drupalSettings Active to follow the best practices proposed here. Experience Builder aims to follow the best practices @catch deduced after years of being a release manager, often having had to deal with the fallout of when the best practices were not followed.
See https://git.drupalcode.org/project/experience_builder/-/merge_requests/1....
- 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
What's interesting here is that AFAICT we basically need the exact same pattern as what's proposed here for default content exported for a Recipe? 😅
Given https://www.drupal.org/node/3533854 → for ✨ Add a command-line utility to export content in YAML format Active , that just became a lot more important 😇 So: bumping priority.
