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.

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

chore: (#45) Fix failing java tests #46

Merged
merged 3 commits into from
Dec 16, 2024
Merged

Conversation

OT-kraftchain
Copy link
Member

No description provided.

Copy link
Member

@mialbu mialbu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Functionally everything looks good. 👍🏼

The main point I’d like to raise is that we generally avoid using wildcard imports, so I’d prefer if we use concrete imports instead. Other than that, I just have a few suggestions. Please take a look at my comments!

@OT-kraftchain OT-kraftchain requested a review from mialbu December 12, 2024 09:45
Copy link
Member

@mialbu mialbu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The new format rules seem not to be applied to the contract class files GrantSharesGove.java and GrantSharesTreasury.java. Please apply it on these files as well.

suggestion: Also, consider removing WRAP_WHEN_TYPING_REACHES_RIGHT_MARGIN in the code style. This would keep long literal strings like the one in the @ContractSourceCode in a single string without having + operators to wrap it.

@mialbu
Copy link
Member

mialbu commented Dec 12, 2024

suggestion: Also, consider removing WRAP_WHEN_TYPING_REACHES_RIGHT_MARGIN in the code style. This would keep long literal strings like the one in the @ContractSourceCode in a single string without having + operators to wrap it.

Maybe we should only do this in non-code files though. I renounce my suggestion.

@OT-kraftchain
Copy link
Member Author

suggestion: Also, consider removing WRAP_WHEN_TYPING_REACHES_RIGHT_MARGIN in the code style. This would keep long literal strings like the one in the @ContractSourceCode in a single string without having + operators to wrap it.

Maybe we should only do this in non-code files though. I renounce my suggestion.

This doesn't seem to be doing what you expected. I set that to false and it's still wraping the string literals that are annotation parameters. I'll search for a different option

@mialbu
Copy link
Member

mialbu commented Dec 12, 2024

This doesn't seem to be doing what you expected. I set that to false and it's still wraping the string literals that are annotation parameters. I'll search for a different option

Hmm, for me, with the line, it looks like this:

@ContractSourceCode(
        "https://github.com/AxLabs/grantshares-contracts/blob/main/src/main/java/com/axlabs/neo/grantshares" +
                "/GrantSharesGov.java")

and like this without it:

@ContractSourceCode(
        "https://github.com/AxLabs/grantshares-contracts/blob/main/src/main/java/com/axlabs/neo/grantshares/GrantSharesGov.java")

@OT-kraftchain
Copy link
Member Author

yes, same for me, what I was saying is that even disabling that, it still formats it the same, breaking the string

@gsmachado
Copy link
Member

@OT-kraftchain is this ready to merge?

@gsmachado gsmachado requested a review from mialbu December 16, 2024 13:24
Copy link
Member

@mialbu mialbu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👌🏼

@OT-kraftchain OT-kraftchain merged commit 905e359 into develop Dec 16, 2024
1 check passed
@OT-kraftchain OT-kraftchain deleted the chore/45_fix_tests branch December 16, 2024 15:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants