TypeScript/tests/cases/fourslash/codeFixChangeJSDocSyntax5.ts

// @strict: true
/// <reference path='fourslash.ts' />
//// var x: [|?number|] = 12;

verify.codeFix({
    description: "Change '?number' to 'number | null'",
    errorCode: 8020,
    index: 0,
    newRangeContent: "number | null",
});
Update jsdoc codefix tests; test function(...) syntax 2017-07-17 23:11:06 +02:00			`// @strict: true`
Codefix for ?! pre/postfix JSDoc types For ?, provide two code fixes, one for jsdoc/closure semantics (`?t -> t \| null)` and one for flow semantics (`?t -> t \| null \| undefined`). The current way of doing this is the hackiest thing you can imagine, but it was easier than lifting everything into the list monad for a code fix that I might not actually keep. 2017-07-17 20:06:20 +02:00			`/// <reference path='fourslash.ts' />`
			`//// var x: [\|?number\|] = 12;`

Replace more 'verify.rangeAfterCodeFix' with 'verify.codeFix' (#18800) 2017-10-10 20:28:05 +02:00			`verify.codeFix({`
Remove periods from refactor/quickfix messages (#20237) * Fix #19959 and #19958: Remove un-localizable messages * Update message * Reorder error messages * Fix https://github.com/Microsoft/TypeScript/issues/15399: remove periods at the end of messages * Accept baselines for error code changes * accept baselines for removed periods * Update diagnostic messages 2017-12-02 01:38:59 +01:00			`description: "Change '?number' to 'number \| null'",`
Replace more 'verify.rangeAfterCodeFix' with 'verify.codeFix' (#18800) 2017-10-10 20:28:05 +02:00			`errorCode: 8020,`
			`index: 0,`
			`newRangeContent: "number \| null",`
			`});`