Fixed comparison to be !== and not !=

also, fixed the same issue for machine-related issues and added documentation.
This commit is contained in:
Shay Nehmad 2019-04-16 16:36:43 +03:00
parent b714ef7a36
commit 93b0c34f07
1 changed files with 7 additions and 4 deletions

View File

@ -404,14 +404,17 @@ class ReportPageComponent extends AuthComponent {
generateReportRecommendationsSection() { generateReportRecommendationsSection() {
return ( return (
<div id="recommendations"> <div id="recommendations">
{Object.keys(this.state.report.recommendations.domain_issues).length !=0 ? {/* Checks if there are any domain issues. If there are more then one: render the title. Otherwise,
* don't render it (since the issues themselves will be empty. */}
{Object.keys(this.state.report.recommendations.domain_issues).length !== 0 ?
<h3>Domain related recommendations</h3> : null } <h3>Domain related recommendations</h3> : null }
<div> <div>
{this.generateIssues(this.state.report.recommendations.domain_issues)} {this.generateIssues(this.state.report.recommendations.domain_issues)}
</div> </div>
<h3> {/* Checks if there are any issues. If there are more then one: render the title. Otherwise,
Machine related Recommendations * don't render it (since the issues themselves will be empty. */}
</h3> {Object.keys(this.state.report.recommendations.issues).length !== 0 ?
<h3>Machine related recommendations</h3> : null }
<div> <div>
{this.generateIssues(this.state.report.recommendations.issues)} {this.generateIssues(this.state.report.recommendations.issues)}
</div> </div>