We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
toString Generator shows fields in the wrong order leading to code generated in the wrong order too.
Fields should show in correct order like the constructor.
The text was updated successfully, but these errors were encountered:
@CsCherrYY Looks like another code action ux related issue. Guess you might be interested in this. :)
Sorry, something went wrong.
we now get the candidate list via ITypeBinding.getDeclaredFields(): https://github.com/eclipse/eclipse.jdt.ls/blob/726ece1d1fd26480028c217f1d27193f4cd05760/org.eclipse.jdt.ls.core/src/org/eclipse/jdt/ls/core/internal/handlers/JdtDomModels.java#L60
ITypeBinding.getDeclaredFields()
The return array seems to not be in particular order. Maybe IType.getFields() returns the correct definition order.
IType.getFields()
Successfully merging a pull request may close this issue.
Environment
Description
toString Generator shows fields in the wrong order leading to code generated in the wrong order too.
Expected result:
Fields should show in correct order like the constructor.
The text was updated successfully, but these errors were encountered: