Egon Okerman d1417e82f8
Modify CWE and OWASP Top 10 links to follow standard link format (APPSEC-1134) (#3529)
* Fix all CWE references

* Fix all OWASP references

* Fix missing CWE prefixes
2024-01-15 17:15:56 +01:00

54 lines
1.2 KiB
Plaintext

== Why is this an issue?
Every call to a function with a non-void return type is expected to return some value. If there is no value that's valid, you should ``++return undefined;++`` rather than using a void return (``++return;++``). Conversely, every call to a function with a void return type is expected to not return any value, even ``++undefined++``.
This rule raises an issue when ``++undefined++`` is returned from a void function, and when void is returned from a non-void function.
=== Noncompliant code example
[source,javascript]
----
function nonvoidFunction(): number | undefined {
return; // Noncompliant
}
function voidFunction(): void {
return undefined; // Noncompliant
}
----
=== Compliant solution
[source,javascript]
----
function nonvoidFunction(): number | undefined {
return undefined;
}
function voidFunction(): void {
return;
}
----
== Resources
* CWE - https://cwe.mitre.org/data/definitions/394[CWE-394 - Unexpected Status Code or Return Value]
ifdef::env-github,rspecator-view[]
'''
== Implementation Specification
(visible only on this page)
include::../message.adoc[]
'''
== Comments And Links
(visible only on this page)
include::../comments-and-links.adoc[]
endif::env-github,rspecator-view[]