From fa046e8ef32a9bace2d74826fff82a42a0897f17 Mon Sep 17 00:00:00 2001 From: "Andrii Doroshenko (Xrayez)" Date: Thu, 2 Sep 2021 16:01:18 +0300 Subject: [PATCH] Use "Prefer local solutions" in best practices for engine contributors Stating that "Solution must be local" is denying the fact that some problems cannot be solved locally. Therefore, documentation should recommend contributors to first look at solutions which are closer to the problem first, and only go for solution that touch core if a problem cannot be solved locally, for instance. --- .../contributing/best_practices_for_engine_contributors.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/community/contributing/best_practices_for_engine_contributors.rst b/community/contributing/best_practices_for_engine_contributors.rst index 60ccdb8ba..204bf832e 100644 --- a/community/contributing/best_practices_for_engine_contributors.rst +++ b/community/contributing/best_practices_for_engine_contributors.rst @@ -191,8 +191,8 @@ In real-life scenarios, these use cases will be at most rare and uncommon anyway, so it makes sense a custom solution needs to be written. This is why it's important to still provide users the basic building blocks to do it. -#7: Solutions must be local -~~~~~~~~~~~~~~~~~~~~~~~~~~~ +#7: Prefer local solutions +~~~~~~~~~~~~~~~~~~~~~~~~~~ When looking for a solution to a problem, be it implementing a new feature or fixing a bug, sometimes the easiest path is to add data or a new function in the