Refactoring the code base for better Quality

[eyeamkd]

• [x] Added Better ESLint Rules
• [x] Removed Redundant Code
• [x] Replaced usage of plain strings with constants
• [x] Improved Documentation
• [x] Separated RenderId generation Logic
• [x] Added Custom Logger with Flags
• [x] Added Unit Test Cases
• [x] Adding RTL Test Cases
• [x] Added PrePush Hook to prevent contributors from commiting bad code
• [x] For every PR placed, the Test Coverage now appears on the comments
• [ ] Adding Documentation on the Test App and explaining how to test the library
• [x] Added Defined Schema for Push Data; Documentation about the same

[eyeamkd]

Test Coverage Report

Lines: 97.36% (74/76) Statements: 97.61% (82/84) Functions: 91.66% (11/12) Branches: 93.1% (27/29)

[eyeamkd]

Test Coverage Report

Lines: 97.36% (74/76) Statements: 97.61% (82/84) Functions: 91.66% (11/12) Branches: 93.1% (27/29)

[eyeamkd]

Test Coverage Report

Lines: 97.36% (74/76) Statements: 97.61% (82/84) Functions: 91.66% (11/12) Branches: 93.1% (27/29)

[eyeamkd]

Test Coverage Report

Lines: 97.36% (74/76) Statements: 97.61% (82/84) Functions: 91.66% (11/12) Branches: 93.1% (27/29)

[eyeamkd]

Test Coverage Report

Lines: 100% (75/75) Statements: 100% (83/83) Functions: 100% (12/12) Branches: 93.1% (27/29)

[eyeamkd]

Test Coverage Report

Lines: 100% (75/75) Statements: 100% (83/83) Functions: 100% (12/12) Branches: 93.1% (27/29)

[balajikummari]

should improve type system for publishing experiments

publishExperimentResult("", "", backendUrl, eventType);

this is not good.

here is a sample type system that I was talking about on call, that has good type safety powred by TS inference

[eyeamkd]

Test Coverage Report

Lines: 89.53% (77/86) Statements: 89.47% (85/95) Functions: 92.3% (12/13) Branches: 86.66% (26/30)