- Issue created by @thejimbirch
- Status changed to Postponed: needs info
5 months ago 6:42am 28 August 2024 - 🇪🇸Spain plopesc Valladolid
Hello Jim!
Thank you for flagging this possible problematic scenario.
Checked other config entities provided by core modules, like views or blocks, and they don't have an explicit dependency to the module that provides the entity type.
From my point of view, it should not be necessary to add the explicit dependency on dashboard module in dashboard config entities.
However, you might have found an scenario where this is generating any issue, it should be addressed.
If that's the case, please report the steps to reproduce the issue and we could determine the best way to solve it.
- Status changed to Closed: works as designed
5 months ago 12:29pm 30 August 2024 - 🇺🇸United States thejimbirch Cape Cod, Massachusetts
I asked about this in the Recipes channel of the Drupal slack, and config expert bircher stated:
the first part ie the module name is an implicit dependency
that is the module where the config entity is defined, it will always implicitly depend on that module
https://drupal.slack.com/archives/C2THUBAVA/p1724847485173839?thread_ts=...
So the name itself is an even stricter check on dependencies and it is not needed in the file.
Thanks for your attention, I will close this as works as designed.