Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Make Enums Statically Imported #87

Open
GoogleCodeExporter opened this issue Jul 3, 2015 · 1 comment
Open

Make Enums Statically Imported #87

GoogleCodeExporter opened this issue Jul 3, 2015 · 1 comment
Labels
auto-migrated Type-Enhancement
Milestone
Low

Comments

@GoogleCodeExporter
Copy link 

What steps will reproduce the problem?

The AFU current inserts enum values using the enum name:
void test(@Sink({FlowPermission.CONDITIONAL}) boolean b1

It would be cleaner if the AFU would statically import the enum so that the 
output was:
void test(@Sink({CONDITIONAL}) boolean b1

Original issue reported on code.google.com by [email protected] on 30 Apr 2014 at 6:07
@GoogleCodeExporter
Copy link
Author

Original comment by [email protected] on 12 Jun 2015 at 9:54

  • Added labels: Priority-Low, Type-Enhancement
  • Removed labels: Priority-Medium, Type-Defect

@mernst mernst added this to the Low milestone Jan 10, 2016
cushon pushed a commit to cushon/annotation-tools that referenced this issue Jun 26, 2023
@dependabot
Bump com.github.johnrengelman.shadow in /annotation-file-utilities (t…
2a5959b 
…ypetools#87)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Type-Enhancement
Projects
None yet
Milestone
Low
Development

No branches or pull requests
2 participants
@mernst @GoogleCodeExporter