-
Notifications
You must be signed in to change notification settings - Fork 29.1k
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
This update switch statement has bug #25971
Labels
*as-designed
Described behavior is as designed
info-needed
Issue requires more information from poster
javascript
JavaScript support issues
upstream
Issue identified as 'upstream' component related (exists outside of VS Code)
Comments
mjbvz
added
javascript
JavaScript support issues
info-needed
Issue requires more information from poster
labels
May 5, 2017
Can you please share a code example |
AMEN.
…On May 5, 2017 1:01 AM, "黄书乐" ***@***.***> wrote:
I'm very sorry, it's my own problem,but It doesn't make sense to “break”
after “return”, I'think "warning" a little bit better than "error".
[image: code_2017-05-05_13-49-37]
<https://cloud.githubusercontent.com/assets/9822645/25735020/d4188786-319a-11e7-98f0-5f6460f7ebc1.png>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#25971 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AZix-NgW7umG0RLr-92oTt-KB-4iNsAsks5r2rsqgaJpZM4NRcP6>
.
|
.
AMEN.
…On May 5, 2017 1:02 AM, "brendamendez34" ***@***.***> wrote:
AMEN.
On May 5, 2017 1:01 AM, "黄书乐" ***@***.***> wrote:
> I'm very sorry, it's my own problem,but It doesn't make sense to “break”
> after “return”, I'think "warning" a little bit better than "error".
> [image: code_2017-05-05_13-49-37]
> <https://cloud.githubusercontent.com/assets/9822645/25735020/d4188786-
319a-11e7-98f0-5f6460f7ebc1.png>
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#25971 (comment)
>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-
auth/AZix-NgW7umG0RLr-92oTt-KB-4iNsAsks5r2rsqgaJpZM4NRcP6>
> .
>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#25971 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AZix-P4TOVTZmqxwTf92h1DAONLYgE2tks5r2rttgaJpZM4NRcP6>
.
|
mjbvz
added
*as-designed
Described behavior is as designed
upstream
Issue identified as 'upstream' component related (exists outside of VS Code)
labels
May 5, 2017
Yes, a more general approach would be better than downgrading this error specifically. TypeScript is tracking user configuration error levels here: microsoft/TypeScript#13408 Closing as as-designed / upstream |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
*as-designed
Described behavior is as designed
info-needed
Issue requires more information from poster
javascript
JavaScript support issues
upstream
Issue identified as 'upstream' component related (exists outside of VS Code)
Steps to Reproduce:
1.In javascript switch statements break will be prompted to unreachable code detected
The text was updated successfully, but these errors were encountered: