Event repo reduced complexity

[saranshisatgit]

Description

This is to reduce the footprint of the function that filters event , I am not sure what else to subtract and divide further, open to suggestions,

Related Issue

#46

Motivation and Context

This would help other contributors to understand code easier and make them to contribute or re-use small footprint

How Has This Been Tested?

Yeah ran unit test and integrations tests both seems fine to me.

Screenshots (if appropriate):

Types of changes

• Non-functional change (docs, style, minor refactor)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my code changes.
• All new and existing tests passed.

[saranshisatgit]

Shit , I mixed my DockerFile railway app here

[cameri]

Shit , I mixed my DockerFile railway app here

Also the package lock changes shouldn't be part of this change.

[coveralls]

Pull Request Test Coverage Report for Build 3454274447

• 11 of 11 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.01%) to 88.678%

---

Totals
Change from base Build 3452290770:	0.01%
Covered Lines:	725
Relevant Lines:	808

---

💛 - Coveralls

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[cameri]

@saranshisatgit I didn't mean remove the package-lock, but instead to revert your changes to it. When comitting please add files individually so unintended changes don't creep up into your commits