Skip to content

Analyzer fails to recognize type literals as valid metadata #14549

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

Closed
rmacnak-google opened this issue Oct 28, 2013 · 2 comments
Closed

Analyzer fails to recognize type literals as valid metadata #14549

rmacnak-google opened this issue Oct 28, 2013 · 2 comments
Labels
closed-as-intended Closed as the reported issue is expected behavior legacy-area-analyzer Use area-devexp instead.
Milestone

Comments

@rmacnak-google
Copy link
Contributor

mirrors/metadata_allowed_values_test/none

@bwilkerson
Copy link
Member

Added this to the M8 milestone.
Removed Priority-Unassigned label.
Added Priority-Medium label.

@rmacnak-google
Copy link
Contributor Author

Sigh. This is now correct behavior as of Issue #14647.


Added AsDesigned label.

@rmacnak-google rmacnak-google added Type-Defect legacy-area-analyzer Use area-devexp instead. closed-as-intended Closed as the reported issue is expected behavior labels Oct 31, 2013
@rmacnak-google rmacnak-google added this to the M8 milestone Oct 31, 2013
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-as-intended Closed as the reported issue is expected behavior legacy-area-analyzer Use area-devexp instead.
Projects
None yet
Development

No branches or pull requests

2 participants