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:
- implement in gecko the schema that does this. (or check that it's implemented)
- remove the aforementioned fallback code
- add migration steps to both gecko and processed profile versioning to add the data to marker schemas from older profiles.
- possibly add tests if there's some missing for this case
┆Issue is synchronized with this Jira Task
In the following code, we have some fallback code dedicated to FileIO markers:
profiler/src/profile-logic/marker-schema.js
Lines 279 to 289 in c87e4e9
This doesn't seem necessary nowadays as this could be implemented as a schema.
The work here is:
┆Issue is synchronized with this Jira Task