Просмотр исходного кода

Fundamental behaviour, not return type

David Baker 1 год назад
Родитель
Сommit
5f1f018a30
1 измененных файлов с 5 добавлено и 5 удалено
  1. 5 5
      code_style.md

+ 5 - 5
code_style.md

@@ -225,11 +225,11 @@ Unless otherwise specified, the following applies to all code:
     }
     ```
 
-37. Avoid functions whose behaviour / return type varies with different parameter types.
-    Multiple return types are fine, but the function's fundamental behaviour should not
-    change according its arguments: have two separate functions. For example, `SDKConfig.get()`
-    with a string param which returns the type according to the param given is ok, but `SDKConfig.get()`
-    with no args returning the whole config object would not be: this should just be a separate function.
+37. Avoid functions whose fundamental behaviour varies with different parameter types.
+    Multiple return types are fine, but if the function's behaviour is going to change significantly,
+    have two separate functions. For example, `SDKConfig.get()` with a string param which returns the
+    type according to the param given is ok, but `SDKConfig.get()` with no args returning the whole
+    config object would not be: this should just be a separate function.
 
 ## React