-
Notifications
You must be signed in to change notification settings - Fork 11
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
Dropping =
prefix (optional type indicator)
#121
Labels
Comments
brettz9
added a commit
to brettz9/jsdoctypeparser
that referenced
this issue
Jul 9, 2020
…eparser#121 BREAKING CHANGE: Removes `=string` type syntax
Nope, this is not supported in Typescript either. |
brettz9
added a commit
that referenced
this issue
Jul 9, 2020
BREAKING CHANGE: Removes `=string` type syntax
brettz9
added a commit
to brettz9/jsdoctypeparser
that referenced
this issue
Jul 9, 2020
brettz9
added a commit
to brettz9/jsdoctypeparser
that referenced
this issue
Jul 9, 2020
brettz9
added a commit
to brettz9/jsdoctypeparser
that referenced
this issue
Jul 9, 2020
…nalTypeExpr` rule; fixes jsdoctypeparser#121 BREAKING CHANGE: Removes `=string` type syntax
brettz9
added a commit
to brettz9/jsdoctypeparser
that referenced
this issue
Jul 9, 2020
…nalTypeExpr` rule; fixes jsdoctypeparser#121 BREAKING CHANGE: Removes `=string` type syntax
brettz9
added a commit
to brettz9/jsdoctypeparser
that referenced
this issue
Jul 9, 2020
…nalTypeExpr` rule; fixes jsdoctypeparser#121 BREAKING CHANGE: Removes `=string` type syntax
brettz9
added a commit
to brettz9/jsdoctypeparser
that referenced
this issue
Jul 9, 2020
…nalTypeExpr` rule; fixes jsdoctypeparser#121 BREAKING CHANGE: Removes `=string` type syntax
brettz9
added a commit
to brettz9/jsdoctypeparser
that referenced
this issue
Jul 9, 2020
…nalTypeExpr` rule; fixes jsdoctypeparser#121 BREAKING CHANGE: Removes `=string` type syntax
brettz9
added a commit
to brettz9/jsdoctypeparser
that referenced
this issue
Jul 9, 2020
…nalTypeExpr` rule; fixes jsdoctypeparser#121 BREAKING CHANGE: Removes `=string` type syntax
brettz9
added a commit
to brettz9/jsdoctypeparser
that referenced
this issue
Jul 9, 2020
…nalTypeExpr` rule; fixes jsdoctypeparser#121 BREAKING CHANGE: Removes `=string` type syntax
brettz9
added a commit
to brettz9/jsdoctypeparser
that referenced
this issue
Jul 9, 2020
…nalTypeExpr` rule; fixes jsdoctypeparser#121 BREAKING CHANGE: Removes `=string` type syntax
brettz9
added a commit
to brettz9/jsdoctypeparser
that referenced
this issue
Apr 21, 2021
…nalTypeExpr` rule; fixes jsdoctypeparser#121 BREAKING CHANGE: Removes `=string` type syntax
brettz9
added a commit
to brettz9/jsdoctypeparser
that referenced
this issue
Apr 24, 2021
…nalTypeExpr` rule; fixes jsdoctypeparser#121 BREAKING CHANGE: Removes `=string` type syntax
sandersn
pushed a commit
that referenced
this issue
Apr 26, 2021
* feat: trigger for `semantic-release`; removed deprecated `PrefixOptionalTypeExpr` rule; fixes #121 BREAKING CHANGE: Removes `=string` type syntax * - Add for CI
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There is the
PrefixOptionalTypeExpr
which indicates as an example=string
(while mentioning it is deprecated--the suffixed version is not), but I don't see this in catharsis or mention of it in Closure docs, so it seems that one should be dropped fromjsdoctypeparser
entirely now, unless TS is using it. (If TS is using it, we could still handle it incheck-syntax
ineslint-plugin-jsdoc
for the other modes.)The text was updated successfully, but these errors were encountered: