From 868b75d5e88e3ca7920eaa140de2ba00f7877ce8 Mon Sep 17 00:00:00 2001 From: Jordi Boggiano Date: Sat, 19 Feb 2022 12:52:00 +0100 Subject: [PATCH] Fix broken links, refs #10542 --- doc/05-repositories.md | 2 +- doc/articles/troubleshooting.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/05-repositories.md b/doc/05-repositories.md index 5f9142a6c..a59f4fbd1 100644 --- a/doc/05-repositories.md +++ b/doc/05-repositories.md @@ -46,7 +46,7 @@ add more repositories to your project by declaring them in `composer.json`. Repositories are only available to the root package and the repositories defined in your dependencies will not be loaded. Read the -[FAQ entry](faqs/why-can't-composer-load-repositories-recursively.md) if you +[FAQ entry](faqs/why-cant-composer-load-repositories-recursively.md) if you want to learn why. When resolving dependencies, packages are looked up from repositories from diff --git a/doc/articles/troubleshooting.md b/doc/articles/troubleshooting.md index 3ccd03536..6e5a4018c 100644 --- a/doc/articles/troubleshooting.md +++ b/doc/articles/troubleshooting.md @@ -94,7 +94,7 @@ indirectly) back on the root package itself, issues can occur in two cases: ## I have a dependency which contains a "repositories" definition in its composer.json, but it seems to be ignored. The [`repositories`](../04-schema.md#repositories) configuration property is defined as [root-only](../04-schema.md#root-package). It is not inherited. You can read more about the reasons behind this in the "[why can't -Composer load repositories recursively?](../faqs/why-can't-composer-load-repositories-recursively.md)" article. +Composer load repositories recursively?](../faqs/why-cant-composer-load-repositories-recursively.md)" article. The simplest work-around to this limitation, is moving or duplicating the `repositories` definition into your root composer.json.