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
I'm not sure why this hasn't been standardised yet, I'm sure there's a good explanation, but basically, the idea is that
typeNullable<T>=T|null|undefined;
be introduced into the standard list of types.
Secondary Suggestion
I also happened to notice that variables cannot be marked with ? directly. My suggestion would be that
letx?: number;
translates to
letx: Nullable<number>;
List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily and help provide feedback.
✅ Viability Checklist
My suggestion meets these guidelines:
This wouldn't be a breaking change in existing TypeScript/JavaScript code
This wouldn't change the runtime behavior of existing JavaScript code
This could be implemented without emitting different JS based on the types of the expressions
This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
Suggestion
Primary Suggestion
I'm not sure why this hasn't been standardised yet, I'm sure there's a good explanation, but basically, the idea is that
be introduced into the standard list of types.
Secondary Suggestion
?
directly. My suggestion would be thattranslates to
List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily and help provide feedback.
✅ Viability Checklist
My suggestion meets these guidelines:
⭐ Suggestion
Basically I want to be able to do:
The text was updated successfully, but these errors were encountered: