On MacOS, when you remediate one or more files and enable debug logging, FileType.<TYPE> is output

[davidnuzik]

v3.0.2rc1 v3.0.1

Summary: On MacOS, if you remediate one or more files, whether they are core, a theme, or a plugin, words like "core", "plugin", "theme" now read as "FileType." for example "FileType.CORE", "FileType.PLUGIN", "FileType.THEME".

This did not occur on Linux during my testing.

Steps to Reproduce:

1. In a MacOS environment, remediate one or more known files. Core or theme or plugin. Ensure you enable debug logging.

Expected Result: I expected to see the same output as on Linux when using the binary. ("plugin" or "theme" or "core")

Actual Result: I see output like "FileType.PLUGIN" for example.

Additional Info: Pre-existing issue. This was reproduced on v3.0.1 as well.

[davidnuzik]

v3.0.2rc2

SUMMARY: QA validation PASSED. I no longer see automation tests failing and when I manually test restoration of any core, plugin, or theme file(s) they now read as normal (like "plugin", "theme", "core" without the "FileType" and all caps).

VALIDATION STEPS

1. Execute automation on MacOS. All passes. Check Linux as well. All passes.
2. Manually remediate 1 or more files of each type: core, plugin, and theme. I chose random ones. This works as expected now both on Mac and Linux without any issues.

NOTES: Note, Linux was working prior but both were checked to ensure nothing else broke.