πŸ‡ΊπŸ‡ΈUnited States @Mixologic

Portland, OR
Account created on 13 November 2008, about 16 years ago
#

Recent comments

πŸ‡ΊπŸ‡ΈUnited States Mixologic Portland, OR

I do not know what is wrong with the patch in #274, but it is filling the disk on a testbot with errors, and then the zombie bot lives on and fails a bunch of builds.

Can you please run some of those tests locally first? Something is fundamentally broken with that patch.

https://dispatcher.drupalci.org/job/drupal_patches/10430/consoleFull is an example of a job that filled the disk.

πŸ‡ΊπŸ‡ΈUnited States Mixologic Portland, OR

Re: #170#171 The general consensus on ✨ Replace .info.yml with composer.json for extensions Postponed is that we are not planning on it being an either/or scenario. The plan is to only deprecate the core key, and the dependencies/test_dependencies keys, and leave .info.yml files, the bulk of that work is actually being done in #3005229: Provide optional support for using composer.json for dependency metadata β†’ .

This is because we are not interested in overloading composer.json to be a metadata storage facility, and instead only want to rely on it for dependency resolution purposes. .yml files are vastly superior to .json files for configuration.

πŸ‡ΊπŸ‡ΈUnited States Mixologic Portland, OR

Re #158 Drupal's ability to work in multiple languages is one of its strongest features. I would say that we probably definitely want to be able to translate commands.

πŸ‡ΊπŸ‡ΈUnited States Mixologic Portland, OR

So this issue probably either needs an issue summary update or needs to be considered 'closed' and some new issues opened.

We have a symfony console CLI in core now. It lives at /core/scripts/drupal . and currently does not conflict with /vendor/bin/drupal from symfony console. If we need to solve that, we should do it in another issue.

We add two different types of console commands: Those which require a booted Drupal, and those which don't

The current CLI app supports "those which don't" - there are patches on this issue which were attempting to support 'those that do'. I believe we should open a new issue to add that bootstraping command separately.

Once we have a way to do bootstrapping commands with core natively, we can clean up the junk store of scripts we currently have: #2289405: [META] Port all shell scripts to console commands β†’

But, IMO, we've solved the issue title "Integrate Symfony Console component to natively support command line operations" -> that is done.

Production build 0.71.5 2024