Hawkeye Tenderwolf
Hawkeye Tenderwolf
I posted these comments on the PR but they should live here: --- Adding `component` into the `installer-types` and library path definition would also add support for all the packages...
Adding `component` into the `installer-types` and library path definition would also add support for all the packages in the [components org](https://github.com/components) on Packagist proper.
This approach doesn't work for contrib modules right now because they can't safely require asset-packagist dependencies. Per the [composer docs](https://getcomposer.org/doc/05-repositories.md#repository): > Repositories are only available to the root package and...
@dxii, the `8.5.3` tag of this project was created about 15-30 minutes after the Drupal core release came out, so you should not be seeing this error anymore. However, on...
@olets, it does? What am I missing? I get: > TwigException: include function does not exist and is not defined in the context
Hmmm, that could be interesting. PDB works on components, repeatable chunks of "web" (CSS, JS, HTML). So if a given field represents a component, then yeah it makes sense. Paragraphs...
Do you have any particular format in mind (json?) or example for what the "file of known issues" would look like? Thanks! 🙏🏻
cc @deviantintegral
lol, from the `drupal-attribute` project README: > ## Why would I need this? > If you're wondering, you probably don't need this.
The idea of using a function is that we actually do want to implement it differently in Drupal land vs. the others. This would let us set up one definition...