-
Notifications
You must be signed in to change notification settings - Fork 244
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
jsii: it is possible to define a method/ctor with non-optional after an optional #301
Comments
eladb
pushed a commit
that referenced
this issue
Nov 8, 2018
Fixes #301: reject non-optional arguments after optional arguments Fixes #298: show default values for optional properties Fixes #302: omit "abstract" from interface properties (they are by definition abstract) Fixes #300: indicate optionals with "optional" instead of "or undefined" Fixes #299: render multiple jsdoc lines as multiple lines in sphinx
eladb
pushed a commit
that referenced
this issue
Nov 8, 2018
Fixes #301: reject non-optional arguments after optional arguments Fixes #298: show default values for optional properties Fixes #302: omit "abstract" from interface properties (they are by definition abstract) Fixes #300: indicate optionals with "optional" instead of "or undefined" Fixes #299: render multiple jsdoc lines as multiple lines in sphinx
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Probably a typescript bug, but it is now possible to define something like this:
This means that
arg1
is optional andarg2
is required, which doesn't work.The text was updated successfully, but these errors were encountered: