From e57f4dca59cc82fa55e5f7b170c4778d8b9f4de3 Mon Sep 17 00:00:00 2001 From: schlak Date: Thu, 20 Jul 2023 10:48:23 +0200 Subject: [PATCH] Update 0006-local-dependency-resolution.md Small typo --- rfcs/0006-local-dependency-resolution.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rfcs/0006-local-dependency-resolution.md b/rfcs/0006-local-dependency-resolution.md index 95d30a0a8c..612a0b4697 100644 --- a/rfcs/0006-local-dependency-resolution.md +++ b/rfcs/0006-local-dependency-resolution.md @@ -245,7 +245,7 @@ This concept overrides the path from which single projects are used. However, in **Example:** Given a project with a dependency to framework library `sap.m` in version `1.108.0`. When overriding the resolution of `sap.m` to a local copy, which defines an additional dependency to another framework library like `sap.ui.codeeditor` in its package.json (or ui5.yaml for SAPUI5 libraries), that dependency might not be available and an error will be thrown. -Such cases can be resolved by temporarily adding the missing library to the dependencies of the root project. In general, once a dependency is part of the "normal" dependency graph of the project, in can also be referenced by projects resolved via workspace resolutions. +Such cases can be resolved by temporarily adding the missing library to the dependencies of the root project. In general, once a dependency is part of the "normal" dependency graph of the project, it can also be referenced by projects resolved via workspace resolutions. ## Alternatives