Linting warnings in some typescript files about cvat HOT 5 OPEN

@bsekachev What do you think about this one, can I work on this?

from cvat.

Hello,
Are you going to fix all typescript warnings in the product?
Or just enable linting? The second option will not really work well for people who deliver new features because they will also need to fix existing errors and warnings.

from cvat.

No @bsekachev, I think linting is already enabled, there are some typescript warnings in some files, I noticed these initially when I was working on my issue which was previously assigned to me, so the first option, fixing all typescript errors in the product.

from cvat.

Under linting I actually meant adding one more stage on git pre-commit (now it runs eslint on changed files, for example). But typescript must run for all the files, because if we change type in one file, it may easily affect many other.. And adding a new action on GitHub.

from cvat.

Yes, so there are some typescript warnings right now, for example, there are some types which are not added in the code, the code runs fine without those types but, it throws some warnings, =>

in this image we just need to add a return type which would be void in this case to remove the warning.
I'm looking to fix such errors and not add any new action on GitHub as that would cause problems for other contributors and their workflows.
So, @bsekachev should I work on this? Please let me know if this needs some more explanation.

from cvat.