aboutsummaryrefslogtreecommitdiff
path: root/website/templates/features/GetterSetter.html
diff options
context:
space:
mode:
Diffstat (limited to 'website/templates/features/GetterSetter.html')
-rw-r--r--website/templates/features/GetterSetter.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/website/templates/features/GetterSetter.html b/website/templates/features/GetterSetter.html
index 7ceaa3ba..1baa5bd0 100644
--- a/website/templates/features/GetterSetter.html
+++ b/website/templates/features/GetterSetter.html
@@ -62,7 +62,7 @@
</p><p>
You can annotate a class with a <code>@Getter</code> or <code>@Setter</code> annotation. Doing so is equivalent to annotating all non-static fields in that class with that annotation. <code>@Getter</code>/<code>@Setter</code> annotations on fields take precedence over the ones on classes.
</p><p>
- Using the <code>AccessLevel.NONE</code> access level simply generates nothing. It's useful only in combination with <a href="features/Data"><code>@Data</code></a> or a class-wide <code>@Getter</code> or <code>@Setter</code>.
+ Using the <code>AccessLevel.NONE</code> access level simply generates nothing. It's useful only in combination with <a href="/features/Data"><code>@Data</code></a> or a class-wide <code>@Getter</code> or <code>@Setter</code>.
</p><p>
<code>@Getter</code> can also be used on enums. <code>@Setter</code> can't, not for a technical reason, but for a pragmatic one: Setters on enums are an extremely bad idea.
</p>