From 13be8acbb77b17d0d0c105c33320ad9496656019 Mon Sep 17 00:00:00 2001 From: Andrii Tserkovnyi Date: Tue, 3 May 2022 16:12:12 +0300 Subject: [PATCH] fix-links --- .../private-api-is-used-on-the-project-level.md | 4 ++-- .../keeping-a-project-upgradable/upgradability-services.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/scos/dev/guidelines/keeping-a-project-upgradable/upgradability-guidelines/private-api-is-used-on-the-project-level.md b/docs/scos/dev/guidelines/keeping-a-project-upgradable/upgradability-guidelines/private-api-is-used-on-the-project-level.md index 80e6d31e8f8..01d0399dbf0 100644 --- a/docs/scos/dev/guidelines/keeping-a-project-upgradable/upgradability-guidelines/private-api-is-used-on-the-project-level.md +++ b/docs/scos/dev/guidelines/keeping-a-project-upgradable/upgradability-guidelines/private-api-is-used-on-the-project-level.md @@ -51,11 +51,11 @@ To resolve the error provided in the example, try the following in the provided 3. Recommended: Extend the functionality using the [Project Modules strategy](/docs/scos/dev/back-end-development/extending-spryker/development-strategies/development-strategies.html#project-modules). 4. Not recommended: Copy the functionality from the core to the project level: 1. Register the missing extension point in [Spryker Ideas](https://spryker.ideas.aha.io/), so we add it in future. - 2. Copy private API core entities to the project level and give them unique names. For an example, see [Example of resolving the error by copying and renaming the entities](#example-of-resolving-the-error-by-copying-and-renaming-the-entities). + 2. Copy private API core entities to the project level and give them unique names. For an example, see [Example of resolving the error by copying and renaming the entities](#example-of-resolving-the-error-by-renaming-private-api-entities). 3. As soon as the extension point in core is released, refactor the code added in step 4.2 using the strategies in steps 1-3. While it's not refactored, auto-upgrades are not supported, and the effort to update the project may be bigger and require more manual work. -## Example of resolving the error by renaming Private API entities +## Example of resolving the error by renaming private API entities 1. Give the method a unique name and copy it to the factory to fetch the business models. In the example, we add `Pyz` to its name, but you can use any other strategy. For example, you can prefix them with your project name. diff --git a/docs/scos/dev/guidelines/keeping-a-project-upgradable/upgradability-services.md b/docs/scos/dev/guidelines/keeping-a-project-upgradable/upgradability-services.md index f4ac806e4ec..8aa51315689 100644 --- a/docs/scos/dev/guidelines/keeping-a-project-upgradable/upgradability-services.md +++ b/docs/scos/dev/guidelines/keeping-a-project-upgradable/upgradability-services.md @@ -51,7 +51,7 @@ The evaluator tool checks the following: To learn more about the evaluator tool, see the following documents: -- [evaluator tool overview](/docs/scos/dev/guidelines/keeping-a-project-upgradable/evaluator-tool-overview.html) + - [Running the evaluator tool](/docs/scos/dev/guidelines/keeping-a-project-upgradable/running-the-evaluator-tool.html)