Fix typos and clarify wording
Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
This commit is contained in:
parent
8ba3f53d2c
commit
f2da5fcf2c
1 changed files with 3 additions and 3 deletions
|
@ -227,9 +227,9 @@ 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 behaviour / return type varies with different parameter types.
|
||||||
Multiple return types are fine, but the function's fundamental behaviour should not
|
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()
|
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 but 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 is not: this could just be a separate function.
|
with no args returning the whole config object would not be: this should just be a separate function.
|
||||||
|
|
||||||
## React
|
## React
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue