From c015071742c741315be015967b7d84b6c2a3667a Mon Sep 17 00:00:00 2001 From: JFronny Date: Mon, 30 Sep 2024 18:06:34 +0200 Subject: [PATCH] docs: remove link to nowhere --- docs/config/libjf-config-compiler-plugin-v2.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/docs/config/libjf-config-compiler-plugin-v2.md b/docs/config/libjf-config-compiler-plugin-v2.md index f6fea00..8870ef8 100644 --- a/docs/config/libjf-config-compiler-plugin-v2.md +++ b/docs/config/libjf-config-compiler-plugin-v2.md @@ -1,8 +1,14 @@ # libjf-config-compiler-plugin-v2 This annotation processor provides finds classes annotated with `@JfConfig` and produces the necessary code and registration for them. Using this is the recommended way to use libjf-config. -Please be aware that the restrictions of [the reflection implementation](./libjf-config-reflect-v1.md) in regard to class loading -will also apply to configs using the plugin if it is loaded during runtime. + +::: warning +If `libjf-unsafe` is present, configs may be accessed early. + +This can lead to issues if your config class accesses other classes that are not yet intended to be accessed. + +Make sure to only access classes that are safe to access early (e.g. JDK classes). +::: Please note that your `fabric.mod.json` must reference the generated class, not your original config. If you plan on accessing your config before `onInitialize`, it is recommended that you call `.ensureInitialized()` on your