Geoff Swift

XML metacharacters are not escaped in the `failure` element's `message` attribute either. Can be reproduced by having a test which throws an exception with a message containing XML metacharacters, e.g....

`getRecordNotifyChange` is deprecated in favour of `notifyRecordUpdateAvailable` refer to https://developer.salesforce.com/docs/platform/lwc/guide/reference-get-record-notify.html Maybe for this reason `getRecordNotifyChange` shouldn't be supported

We had problems with our JavaScript only code base flagging up warnings like so... ``` Use object shorthand or index signatures instead of `Object`, e.g., `{[key: string]: string}` jsdoc/check-types ```...

Some overlap with my report in #219

Will this be supported by sfdx-lwc-jest, or is the expectation that we need to apply a workaround via `jest.config.js`

I'm happy with the fix. I don't need my workaround any longer.

@soridalac Here's a minimal reproduction... ``` ~/src/cpm$ echo '63.0Deleted' > force-app/deprecated/classes/Test.cls-meta.xml ~/src/cpm$ echo 'public class Test {}' > force-app/deprecated/classes/Test.cls ~/src/cpm$ sf project deploy start -c ─────────────── Deploying Metadata ─────────────── Deploying...

From the log you should hopefully see it's trying to remove something from the org which was never actually there. Once you get yourself into this state, you can't push...

Can we make the autofix rewrite the code like that? As it stands the autofix seems to make the code worse.

This is related / similar to https://github.com/jest-community/eslint-plugin-jest/issues/1198