I don't think this one needs discussion. Just action. This has been very close to RTBC for a long time. Does anyone have any final comments? Can someone do a code review? I would really like to see this in 1.29.
Just want to ask if this one would be eligble for bugfix release? If so, is it close to complete?
Provide more complete template suggestions for entities in a standardized way
https://github.com/backdrop/backdrop-issues/issues/6651
It seems that this PR is currently blocked, because of a possible (but unidentified) better way to accomplish the task.
Do we need a different solution that the one provided here?
Is this is an issue worth pursuing? Is there even interest in this idea?
I'd like to discuss options for moving #2231 forward. It concerns having a simplified array syntax for database details that will support complex passwords better than the current db url and simpler than the D7 way.
There is a PR, but it is blocked when we get to trying to parse and write at install time. Greg (@klonos) proposed a better way of reading and writing settings.php by using token_get_all() in #6297 but that seems to have stalled.
I wonder whether splitting off the task into just supporting a simplified array and documenting that it is supported without changing the install process is the way to go to get some movement on this?
Comments
Design / UX topics?
Some things that could get into the next release, if they make sense. Some of them are just ideas that need feedback.
A couple of text relelated ideas that MIGHT help make the layout system easier to use for some folks.
I don't think this one needs discussion. Just action. This has been very close to RTBC for a long time. Does anyone have any final comments? Can someone do a code review? I would really like to see this in 1.29.
Developer Meeting:
I'd like to discuss options for moving #2231 forward. It concerns having a simplified array syntax for database details that will support complex passwords better than the current db url and simpler than the D7 way. There is a PR, but it is blocked when we get to trying to parse and write at install time. Greg (@klonos) proposed a better way of reading and writing settings.php by using token_get_all() in #6297 but that seems to have stalled. I wonder whether splitting off the task into just supporting a simplified array and documenting that it is supported without changing the install process is the way to go to get some movement on this?