Question: Would it be beneficial to use vscode-ddev-manager for exposing binaries in the container to the host?

[rpkoller]

At first thank you for creating and working on this addon (forgot to note that on my initial issue apologies). After watching the recording of your Florida Drupal Camp talk i wonder about one detail. There you've mentioned you have created a wrapper for translating the host and container paths.

The detail I wonder about is, are those wrappers even necessary at least if the addon is used in combination with VSCode? Cuz there, there is the vscode-ddev-manager extension. since version 3.x there is the option to expose binaries within the container and make them directly useable in the frontend. @stasadev outlines how the feature is used in the following comment: ddev/vscode-ddev-manager#11 (comment) . therefor i wonder if that would be actually useful for ddev-drujpal-code-quality and could saves you a bit of complexity? if not please ignore the issue and close.

[UltraBob]

@rpkoller Thank you. I need to research that. I don't think I was aware of it. I am considering adding an alias to make host paths work in the container which would reduce the need for a lot of this. My goal is to make this work without the need for any specific setup, and one of my nearterm improvements will hopefully be starter configs for other IDEs as well, so I'm not sure the vscode-ddev-manager-extension will be a workable solution, but at minimum, I want to look into how they do what they do.

[UltraBob]

Also @rpkoller thanks for checking out the talk! I'm excited to have you trying it out.

[rpkoller]

@UltraBob yep agreed just wanted make sure you are aware of that solution, cuz it is not communicated very prominently on their repo. but 100% agree that a cross IDE solution would be the preferable choice (maybe their approach is viable candidate for that).

and i havent had much time checking out your addon yet. my main intention was briefly testing it with the local setup i use for core and contrib testing in drupal. i am not a developer, am more into content strategy, ux, and accessibility.; plus being active in the DDEV repo from time to time. over time I've tested all the addons available in the context of contribution:

https://github.com/justafish/ddev-drupal-core-dev
(i dislike that it only allowed testing for core, everything is placed within the project root without an install in the web docroot and therefore drush is not really available, plus having a bespoke selenium container)

https://github.com/ddev/ddev-drupal-contrib
(unfortunately you only have one contrib module per project and again a single repo in the root of the project plus some poser magic).

personally, for testing, i prefer https://github.com/joachim-n/drupal-core-development-project that allows you to have the drupal core repo as well as many other contrib repos as you want. for contrib you have to symlink those repos on composer require same as the core repo is being linked. it has a few minor flaws but overall it is the most useful and low barrier tool for testing MRs in drupal from my experience. i've also created a small addon https://github.com/rpkoller/ddev-drupal-contribution that is automating several steps plus adding the selenium addon by moshe as a dependency. the thing i am still struggling with is to get those tests and tooling working. i'Ve tried to get it working with the selenium container by justafish. but either way i hasnt worked yet. that symlinking makes things a bit more tricky. therefore my hope was maybe it "might" work with your addon. cuz on the paper i dont see why the tooling you have right now shouldnt also work with joachims composer template compared to a site installed with the standard drupal profile. i havent had the time to test your addon in depth. i simply installed your addon after ive installed mine (the only thing i manually removed were the web commands that had name conflicts). the install only had a hickup with cspell and running ddev checks worked in most part it looked like. i would only have to adjust the directories that are being checked. have to revisit for a closer look in the next days when i have time again. just wanted to provide you some background info and context.