91 lines
No EOL
4.2 KiB
JSON
91 lines
No EOL
4.2 KiB
JSON
{
|
|
"uuid": [
|
|
{
|
|
"value": "85b61d26-e598-4b64-99b4-445d8d22fba5"
|
|
}
|
|
],
|
|
"langcode": [
|
|
{
|
|
"value": "en"
|
|
}
|
|
],
|
|
"type": [
|
|
{
|
|
"target_id": "daily_email",
|
|
"target_type": "node_type",
|
|
"target_uuid": "8bde1f2f-eef9-4f2d-ae9c-96921f8193d7"
|
|
}
|
|
],
|
|
"revision_timestamp": [
|
|
{
|
|
"value": "2025-05-11T09:00:05+00:00"
|
|
}
|
|
],
|
|
"revision_uid": [
|
|
{
|
|
"target_type": "user",
|
|
"target_uuid": "b8966985-d4b2-42a7-a319-2e94ccfbb849"
|
|
}
|
|
],
|
|
"revision_log": [],
|
|
"status": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"uid": [
|
|
{
|
|
"target_type": "user",
|
|
"target_uuid": "b8966985-d4b2-42a7-a319-2e94ccfbb849"
|
|
}
|
|
],
|
|
"title": [
|
|
{
|
|
"value": "Should Drush be in Drupal core?"
|
|
}
|
|
],
|
|
"created": [
|
|
{
|
|
"value": "2024-11-07T00:00:00+00:00"
|
|
}
|
|
],
|
|
"changed": [
|
|
{
|
|
"value": "2025-05-11T09:00:05+00:00"
|
|
}
|
|
],
|
|
"promote": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"sticky": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"default_langcode": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"revision_translation_affected": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"path": [
|
|
{
|
|
"alias": "\/daily\/2024\/11\/07\/should-drush-be-in-drupal-core",
|
|
"langcode": "en"
|
|
}
|
|
],
|
|
"body": [
|
|
{
|
|
"value": "\n <p>I've used Drush - the Drupal shell - to interact with my Drupal applications on the command line since I started around 2008.<\/p>\n\n<p>It's always been part of my Drush experience.<\/p>\n\n<p>From installing Drupal and performing routine actions such as enabling modules and clearing caches to, in newer Drupal versions, performing migrations and generating Storybook stories.<\/p>\n\n<p>Many projects I work on have custom Drush commands to perform tasks from the command line.<\/p>\n\n<p>This week, I created a new Drupal 11 project for a client using the <a href=\"https:\/\/github.com\/drupal\/core-recommended\">drupal\/core-recommended<\/a> package and initially forgot to install Drush so I could install Drupal.<\/p>\n\n<p>I'm surprised Drush isn't in Drupal core or a dependency of the recommended package.<\/p>\n\n<p>There is a basic Drupal CLI at <a href=\"https:\/\/git.drupalcode.org\/project\/drupal\/-\/blob\/94bc96150ca726fc667be51c8176f90b56e492df\/core\/scripts\/drupal\">core\/scripts\/drupal<\/a>, but I wonder if we'll see a fully-featured CLI tool like Drush included with Drupal core, similar to Symfony's console or Laravel's artisan commands.<\/p>\n\n<p>For me, including Drush would be an obvious choice.<\/p>\n\n ",
|
|
"format": "full_html",
|
|
"processed": "\n <p>I've used Drush - the Drupal shell - to interact with my Drupal applications on the command line since I started around 2008.<\/p>\n\n<p>It's always been part of my Drush experience.<\/p>\n\n<p>From installing Drupal and performing routine actions such as enabling modules and clearing caches to, in newer Drupal versions, performing migrations and generating Storybook stories.<\/p>\n\n<p>Many projects I work on have custom Drush commands to perform tasks from the command line.<\/p>\n\n<p>This week, I created a new Drupal 11 project for a client using the <a href=\"https:\/\/github.com\/drupal\/core-recommended\">drupal\/core-recommended<\/a> package and initially forgot to install Drush so I could install Drupal.<\/p>\n\n<p>I'm surprised Drush isn't in Drupal core or a dependency of the recommended package.<\/p>\n\n<p>There is a basic Drupal CLI at <a href=\"https:\/\/git.drupalcode.org\/project\/drupal\/-\/blob\/94bc96150ca726fc667be51c8176f90b56e492df\/core\/scripts\/drupal\">core\/scripts\/drupal<\/a>, but I wonder if we'll see a fully-featured CLI tool like Drush included with Drupal core, similar to Symfony's console or Laravel's artisan commands.<\/p>\n\n<p>For me, including Drush would be an obvious choice.<\/p>\n\n ",
|
|
"summary": null
|
|
}
|
|
]
|
|
} |