Repository: oppia/oppia

Issue:
Create a ActionObjectFactory for DebugInfoTrackerService
<!--
  - Thanks for taking the time to report a bug in the Oppia project.
  - Before filing a new issue, please do a quick search to check that it hasn't
  - already been filed on the [issue tracker](https://github.com/oppia/oppia/issues)._
  -->

**Describe the bug**
Currently, there is no proper type of action i.e. what can an action be in DebugInfoTrackerService. There should be a separate ActionObject and update the code to only use that. So, a proper type for `action` can be defined.

Create a ActionObjectFactory for DebugInfoTrackerService
<!--
  - Thanks for taking the time to report a bug in the Oppia project.
  - Before filing a new issue, please do a quick search to check that it hasn't
  - already been filed on the [issue tracker](https://github.com/oppia/oppia/issues)._
  -->

**Describe the bug**
Currently, there is no proper type of action i.e. what can an action be in DebugInfoTrackerService. There should be a separate ActionObject and update the code to only use that. So, a proper type for `action` can be defined.



Discussion:
@kevintab95 As you created this service, I needed your help in understanding what exactly is this service used for, and in general what is an action. Thanks
Hi @nishantwrp, it was initially introduced as a utility tool to capture the sequence of steps the user took before an error occured. This is so that we have more info to debug the error.

I don't think it has a clear "type" but we could standardise it. Considering that #6921 (the issue for which we introduced this service) is closed, we could remove the current usages of it -- if it makes things easier to standardise.

Just wanted to chime in and say that getting rid of it entirely is probably preferable if it's not needed any more -- that is a perfectly acceptable way to solve the issue.
Yep, I agree.
OK, So should I make a PR removing this service completely from the codebase?
@kevintab95 As you created this service, I needed your help in understanding what exactly is this service used for, and in general what is an action. Thanks
Hi @nishantwrp, it was initially introduced as a utility tool to capture the sequence of steps the user took before an error occured. This is so that we have more info to debug the error.

I don't think it has a clear "type" but we could standardise it. Considering that #6921 (the issue for which we introduced this service) is closed, we could remove the current usages of it -- if it makes things easier to standardise.

Just wanted to chime in and say that getting rid of it entirely is probably preferable if it's not needed any more -- that is a perfectly acceptable way to solve the issue.
Yep, I agree.
OK, So should I make a PR removing this service completely from the codebase?

Resolving patch:
diff --git a/scripts/check_frontend_coverage.py b/scripts/check_frontend_coverage.py
--- a/scripts/check_frontend_coverage.py
+++ b/scripts/check_frontend_coverage.py
@@ -103,7 +103,6 @@
     'data.ts',
     'date-time-format.service.ts',
     'debouncer.service.ts',
-    'debug-info-tracker.service.ts',
     'device-info.service.ts',
     'document-attribute-customization.service.ts',
     'drag-and-drop-sort-input-rules.service.ts',


Test patch: