No need to start a debugger to see your fields: Just let lombok generate a
toString for you!
Any class definition may be annotated with
@ToString to let lombok generate an implementation of the
toString() method. By default, it'll print your class name, along with each field, in order, separated by commas.
By setting the
includeFieldNames parameter to true you can add some clarity (but also quite some length) to the output of the
By default, all non-static fields will be printed. If you want to skip some fields, you can annotate these fields with
@ToString.Exclude. Alternatively, you can specify exactly which fields you wish to be used by using
@ToString(onlyExplicitlyIncluded = true), then marking each field you want to include with
callSuper to true, you can include the output of the superclass implementation of
toString to the output. Be aware that the default implementation of
java.lang.Object is pretty much meaningless, so you probably don't want to do this unless you are extending another class.
You can also include the output of a method call in your
toString. Only instance (non-static) methods that take no arguments can be included. To do so, mark the method with
You can change the name used to identify the member with
@ToString.Include(name = "some other name"), and you can change the order in which the members are printed via
@ToString.Include(rank = -1). Members without a rank are considered to have rank 0, members of a higher rank are printed first, and members of the same rank are printed in the same order they appear in the source file.
Supported configuration keys:
false] (default: true)
Normally lombok generates a fragment of the toString response for each field in the form of
fieldName = fieldValue. If this setting is set to
false, lombok will omit the name of the field and simply deploy a comma-separated list of all the field values. The annotation parameter '
includeFieldNames', if explicitly specified, takes precedence over this setting.
false] (default: false)
If set to
true, lombok will access fields directly instead of using getters (if available) when generating
toStringmethods. The annotation parameter '
doNotUseGetters', if explicitly specified, takes precedence over this setting.
error] (default: not set)
Lombok will flag any usage of
@ToStringas a warning or error if configured.
If there is any method named
toString with no arguments, regardless of return type, no method will be generated, and instead a warning is emitted explaining that your
@ToString annotation is doing nothing. You can mark any method with
@lombok.experimental.Tolerate to hide them from lombok.
Arrays are printed via
Arrays.deepToString, which means that arrays that contain themselves will result in
StackOverflowErrors. However, this behaviour is no different from e.g.
If a method is marked for inclusion and it has the same name as a field, it replaces the toString output for that field (the method is included, the field is excluded, and the method's output is printed in the place the field would be printed).
Prior to lombok 1.16.22, inclusion/exclusion could be done with the
exclude parameters of the
@ToString annotation. This old-style inclusion mechanism is still supported but will be deprecated in the future.
@ToString.Include on a member generates a warning; the member will be excluded in this case.
We don't promise to keep the output of the generated
toString() methods the same between lombok versions. You should never design your API so that other code is forced to parse your
toString() output anyway!
By default, any variables that start with a $ symbol are excluded automatically. You can only include them by using the
If a getter exists for a field to be included, it is called instead of using a direct field reference. This behaviour can be suppressed:
@ToString(doNotUseGetters = true)
@ToString can also be used on an enum definition.