-
Notifications
You must be signed in to change notification settings - Fork 426
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
Wildcard in import statements #2
Comments
@iamatinkerer Thank you very much for pointing this out. You are right, it is a good practice to specify classes in imports. We really appreciate your participation and hope you could help us to fix it. |
@v-xiangs
Can I take this issue and send a PR then? |
@iamatinkerer - we are working on getting a development branch created. Once that's available, you can send a PR there. Please stay tuned and thank you for your help 😄 |
@iamatinkerer |
Closing this issue as it is fixed by #52 |
Current changes and fixes to ICR feature
In many files, the import statements use wildcard to import all the classes in the packages
E.g. https://github.com/Microsoft/mssql-jdbc/blob/master/src/main/java/com/microsoft/sqlserver/jdbc/KerbAuthentication.java
import java.util.*;
It is a good practice to specify the specific classes in these imports.
The text was updated successfully, but these errors were encountered: