Fix linting warnings for Function, Boolean and String types

[DerenToy]

Which problem is this PR solving?

• Resolves part of no-unused-vars warnings for [chore]: Fix eslint warnings #1608

Description of the changes

• Fixed ESlint warnings for Function, Boolean and String types

How was this change tested?

• By running "yarn lint" command

Checklist

• I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
• I have signed all commits
• I have added unit tests for the new functionality
• I have run lint and test steps successfully
  • for jaeger: make lint test
  • for jaeger-ui: yarn lint and yarn test

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Files	Coverage Δ
...nitor/ServicesView/operationDetailsTable/index.tsx	100.00% <100.00%> (ø)
...components/TracePage/TraceTimelineViewer/utils.tsx	100.00% <100.00%> (ø)
...jaeger-ui/src/model/ddg/transformTracesToPaths.tsx	100.00% <100.00%> (ø)
packages/jaeger-ui/src/utils/TreeNode.tsx	100.00% <100.00%> (ø)

📢 Thoughts on this report? Let us know!.

[yurishkuro]

This replacement is not completely equivalent. What would be a situation when value would not be a number?

[DerenToy]

Hello,

In this case, the value of 'value' is 'ServiceOpsMetrics['latency']', and 'latency' is defined as a number type.

export type ServiceOpsMetrics = {
dataPoints: OpsDataPoints;
errRates: number;
impact: number;
latency: number;
name: string;
requests: number;
key: number;
};

Therefore, I thought that there is no need for additional type checking because 'value' is always of type number. Am I mistaken?

[yurishkuro]

lgtm, except the question about the first file

[yurishkuro]

Thanks!

[DerenToy]

@yurishkuro 🙏🏻🙏🏻🙏🏻