Fundamental behaviour, not return type
parent
f2da5fcf2c
commit
5f1f018a30
|
@ -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.
|
37. Avoid functions whose fundamental behaviour varies with different parameter types.
|
||||||
Multiple return types are fine, but the function's fundamental behaviour should not
|
Multiple return types are fine, but if the function's behaviour is going to change significantly,
|
||||||
change according its arguments: have two separate functions. For example, `SDKConfig.get()`
|
have two separate functions. For example, `SDKConfig.get()` with a string param which returns the
|
||||||
with a string param which returns the type according to the param given is ok, but `SDKConfig.get()`
|
type according to the param given is ok, but `SDKConfig.get()` with no args returning the whole
|
||||||
with no args returning the whole config object would not be: this should just be a separate function.
|
config object would not be: this should just be a separate function.
|
||||||
|
|
||||||
## React
|
## React
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue