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

GROOVY-5134: @ToString optionally exclude fields with null values #26

Closed
wants to merge 1 commit into from
Closed

Conversation

andresteingress
Copy link
Contributor

this patch adds the "ignoreNullValues" annotation parameter to @tostring. In order to check properties and/or fields for null values, another (hidden) local variable had to be introduced. In addition, I added a test case for testing @tostring in general, not restricted to ignoreNullValues.

@ghost ghost assigned paulk-asert Feb 17, 2012
@paulk-asert
Copy link
Member

Added, thanks for the pull request. Just for the record, there are other tests for @tostring in some of the Canonical tests - we tested several annotations in one hit that way.

@andresteingress
Copy link
Contributor Author

Okay, thanks for the hint. I think I stumbled upon these test cases at some point but thought it wouldn't harm if there would be a dedicated test class.

blackdrag pushed a commit that referenced this pull request Aug 27, 2014
melix pushed a commit to melix/groovy-core that referenced this pull request Jun 7, 2015
The README stated that you should run

    gradlew jarAll idea

before loading the project into IntelliJ IDEA. It seems, though, that the `jarAll`
task breaks the IDE integration and you can't run tests. Running

    gradlew jar idea

seems to work fine, so I've updated the README to reflect this.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants