You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the mutation-testing-elements report loads a language it does not have build-in syntax highlighting for, it will fall back on the autoloader. It will actually download the language highlighting on the spot. This works with the prism autoloader plugin.
However, there is currently no way to register a callback for when syntax highlighting is done. This is vital since we need to attach mutants to the properties of the mutant-components here:
When the mutation-testing-elements report loads a language it does not have build-in syntax highlighting for, it will fall back on the autoloader. It will actually download the language highlighting on the spot. This works with the prism autoloader plugin.
However, there is currently no way to register a callback for when syntax highlighting is done. This is vital since we need to attach mutants to the properties of the mutant-components here:
mutation-testing-elements/packages/mutation-testing-elements/src/components/mutation-test-report-file/index.ts
Line 117 in 20b3eab
The result is that the mutants will not be bound to the
mutation-test-report-mutant
elements which in turn makes the mutants invisibleSee PrismJS/prism#2275
Thanks to @theofidry for pointing this out to me in infection/infection#1149
As a workaround, we should disable autoloading and just add languages whenever we want to support one. We'll be adding php shortly 🤝
The text was updated successfully, but these errors were encountered: