Skip to content

Clean up the fallback label code for FileIO markers #3131

Description

@julienw

In the following code, we have some fallback code dedicated to FileIO markers:

case 'FileIO':
if (data.source) {
description = `(${data.source}) `;
}
description += data.operation;
if (data.filename) {
description = data.operation
? `${description}${data.filename}`
: data.filename;
}
break;

This doesn't seem necessary nowadays as this could be implemented as a schema.
The work here is:

  1. implement in gecko the schema that does this. (or check that it's implemented)
  2. remove the aforementioned fallback code
  3. add migration steps to both gecko and processed profile versioning to add the data to marker schemas from older profiles.
  4. possibly add tests if there's some missing for this case

┆Issue is synchronized with this Jira Task

Metadata

Metadata

Assignees

No one assigned

    Labels

    code maintenanceIssues that are not user facing, but are related the technical debt with the code itselfhelp wantedThings ready to be worked on by anyone. Issues must include instructions on how to complete the taskmarkersAnything to do with marker data structures, marker chart, or the marker tableneeds gecko patchThis issue is blocked by a patch that must land in the Gecko codebase first

    Type

    No type

    Fields

    Priority

    None yet

    Jira

    None yet

    Severity

    None yet

    Estimate

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions