Skip to main content

Error message

Warning: Undefined property: Drupal\markdown\Plugin\Markdown\CommonMark\CommonMarkGfm::$converter in Drupal\markdown\Plugin\Markdown\CommonMark\CommonMarkGfm->converter() (line 53 of modules/contrib/markdown/src/Plugin/Markdown/CommonMark/CommonMarkGfm.php).
Drupal\markdown\Plugin\Markdown\CommonMark\CommonMarkGfm->converter() (Line: 155)
Drupal\markdown\Plugin\Markdown\CommonMark\CommonMark->convertToHtml() (Line: 227)
Drupal\markdown\Plugin\Markdown\BaseParser->parse() (Line: 174)
Drupal\markdown\Plugin\Filter\FilterMarkdown->process() (Line: 122)
Drupal\filter\Element\ProcessedText::preRenderText()
call_user_func_array() (Line: 107)
Drupal\Core\Render\Renderer->doTrustedCallback() (Line: 914)
Drupal\Core\Render\Renderer->doCallback() (Line: 447)
Drupal\Core\Render\Renderer->doRender() (Line: 230)
Drupal\Core\Render\Renderer->render() (Line: 523)
Drupal\Core\Template\TwigExtension->escapeFilter() (Line: 89)
__TwigTemplate_6ae428a222b1a4d544259198ce1da892->doDisplay() (Line: 461)
Twig\Template->yield() (Line: 444)
Twig\Template->render() (Line: 53)
Twig\TemplateWrapper->render() (Line: 35)
Drupal\Core\Template\TwigThemeEngine->renderTemplate() (Line: 428)
Drupal\Core\Theme\ThemeManager->render() (Line: 504)
Drupal\Core\Render\Renderer->doRender() (Line: 517)
Drupal\Core\Render\Renderer->doRender() (Line: 230)
Drupal\Core\Render\Renderer->render() (Line: 523)
Drupal\Core\Template\TwigExtension->escapeFilter() (Line: 106)
__TwigTemplate_a34b76f8bd319a4caf25f6c976ce7cbd->doDisplay() (Line: 461)
Twig\Template->yield() (Line: 444)
Twig\Template->render() (Line: 53)
Twig\TemplateWrapper->render() (Line: 35)
Drupal\Core\Template\TwigThemeEngine->renderTemplate() (Line: 428)
Drupal\Core\Theme\ThemeManager->render() (Line: 504)
Drupal\Core\Render\Renderer->doRender() (Line: 230)
Drupal\Core\Render\Renderer->render() (Line: 242)
Drupal\Core\Render\MainContent\HtmlRenderer->Drupal\Core\Render\MainContent\{closure}() (Line: 638)
Drupal\Core\Render\Renderer::Drupal\Core\Render\{closure}()
Fiber->resume() (Line: 653)
Drupal\Core\Render\Renderer->executeInRenderContext() (Line: 235)
Drupal\Core\Render\MainContent\HtmlRenderer->prepare() (Line: 131)
Drupal\Core\Render\MainContent\HtmlRenderer->renderResponse() (Line: 69)
Drupal\Core\EventSubscriber\MainContentViewSubscriber->onViewRenderArray() (Line: 254)
Symfony\Component\EventDispatcher\EventDispatcher::Symfony\Component\EventDispatcher\{closure}() (Line: 206)
Symfony\Component\EventDispatcher\EventDispatcher->callListeners() (Line: 56)
Symfony\Component\EventDispatcher\EventDispatcher->dispatch() (Line: 200)
Symfony\Component\HttpKernel\HttpKernel->handleRaw() (Line: 77)
Symfony\Component\HttpKernel\HttpKernel->handle() (Line: 54)
Drupal\simple_oauth\HttpMiddleware\BasicAuthSwap->handle() (Line: 53)
Drupal\Core\StackMiddleware\Session->handle() (Line: 30)
Drupal\Core\StackMiddleware\KernelPreHandle->handle() (Line: 28)
Drupal\Core\StackMiddleware\ContentLength->handle() (Line: 32)
Drupal\big_pipe\StackMiddleware\ContentLength->handle() (Line: 203)
Drupal\page_cache\StackMiddleware\PageCache->fetch() (Line: 140)
Drupal\page_cache\StackMiddleware\PageCache->lookup() (Line: 89)
Drupal\page_cache\StackMiddleware\PageCache->handle() (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle() (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle() (Line: 71)
Drupal\Core\StackMiddleware\AjaxPageState->handle() (Line: 54)
Drupal\Core\StackMiddleware\StackedHttpKernel->handle() (Line: 753)
Drupal\Core\DrupalKernel->handle() (Line: 34)
Symfony\Component\Runtime\Runner\Symfony\HttpKernelRunner->run() (Line: 32)
require() (Line: 22)
require_once() (Line: 13)

Composer, the dependency manager for PHP, does supports meta-packages. A meta-package is a package that doesn't contain any actual code or files itself but rather defines a collection of dependencies.

Here's how you can use a meta-package:

1. Define Dependencies: In the composer.json file of the meta-package, you list the packages that you want to include as dependencies. You don't include any actual code, classes, or files in the meta-package itself.

2. Versioning: You can define specific versions or version constraints for the dependencies in the meta-package. This ensures that all the included packages are compatible with each other.

3. Installation: When someone requires your meta-package using Composer, all the defined dependencies will be installed together. It's a convenient way to bundle related packages.

4. Use Case: Meta-packages are often used to bundle together a set of related packages that work well together, such as a framework with its standard plugins or a set of development tools.

Here's an example of what a meta-package's composer.json might look like:

json { "name": "my-vendor/my-metapackage", "type": "metapackage", "require": { "some-vendor/package-one": "^1.0", "another-vendor/package-two": "^2.1" } }

The key here is that the meta-package itself doesn't contain any code. It's just a way to define a set of packages that should be installed together. It's a neat way to keep things organised and ensure compatibility.