Excessive ESLint warnings in frontend container logs make debugging difficult

[vickabire]

Description

The frontend container logs are cluttered with numerous ESLint warnings, including unused variables, empty functions, and unescaped entities. These warnings span multiple files and fill more than a full screen, making it difficult to identify critical log messages and debug effectively.

Example Warnings

• no-unused-vars: Several variables are assigned but never used (e.g., panelTestMap, handleLabValidation, etc.)

• @typescript-eslint/no-empty-function: Functions are defined with no implementation

• react/no-unescaped-entities: Use of unescaped characters in JSX

Some of the files Affected

• src/App.js

• src/components/addOrder/AddOrder.js

• src/components/addOrder/Index.js

• src/components/addOrder/SampleType.js

• src/components/admin/Admin.js

• src/components/admin/BatchTestReassignmentAndCancellation/BatchTestReassignmentAndCancellation.js

Expected Behavior

Logs should be cleaner, with fewer warnings to allow developers to focus on relevant runtime or build issues.

Suggested Actions

• Clean up unused variables and imports

• Remove or implement empty functions

• Escape special characters in JSX properly

• Consider adjusting ESLint rules if certain warnings are deemed non-critical for development

screencast showing the errors

openelisfrontenderror.1.1.mp4