Documentation update

Author: calmilamsy

glass-config-api-v3/docs/Adding.md

@@ -2,4 +2,4 @@
 
 You want to use GCAPI to handle your mod config? Great!
 
-You already have GCAPI in your workspace if you have [StationAPI](../../wiki/Setting-up-workspace). For the next steps, see [Using](Using.md).
+You already have GCAPI in your workspace if you have [StationAPI](../../wiki/Setting-up-workspace). For the next steps, see [Using](Using.md).

glass-config-api-v3/docs/Home.md

@@ -6,4 +6,6 @@
 
 [TODO for GCAPI](Todo.md)
 
-[Migrating from 1.0 to 2.0](Migration1.0.md)
+[Migrating from 1.0 to 2.0](Migration1.0.md)
+
+[Migrating from 2.0 to 3.0](Migration2.0.md)

glass-config-api-v3/docs/Migration1.0.md

@@ -36,4 +36,4 @@ CHANGED:
     - `init(Screen,TextRenderer)V` no longer handles adding icons indicating server sync.
 - `PreConfigSavedListener` and `PostConfigLoadedListener`
     - A new `source` parameter was added.
-    - See `EventStorage.EventSource` for more information.
+    - See `EventStorage.EventSource` for more information.

glass-config-api-v3/docs/Migration2.0.md

@@ -6,4 +6,8 @@ Most breaking changes are package changes, and annotation changes, with only one
 
 - `@ConfigEntry` and `@ConfigCategory` now house all information about the field is on, removing the need for checking for 6 different annotations on load.
 - `@GConfig` had it's `primary` value removed, and instead replaced with `priority`.
-- 
+- All packages have changed to properly follow StationAPI's project structure.
+- Config verification has been moved from clientside classes, and is now applied whenever a config value is loaded.
+- Added a new optional field to `ConfigEntry`: `textValidator`. This will be used by default on any custom config types, unless `isValid` is overridden.
+- Array types now require `getTypedArray` to be overridden due to java type parameter shenanigans.
+- `@ConfigEntry` and `@ConfigCategory` can now use translation keys in their names and descriptions.

glass-config-api-v3/docs/Todo.md

@@ -5,4 +5,4 @@ Mostly for me. In rough order of priority weighted with estimated difficulty.
 2. Add the ability to easily and cleanly edit config fields programmatically.
 3. Add support for colours with an ingame colour picker. Adding an actual colour picker might be a pain the the arse. I have a couple of ideas on how to do this.
 4. Add field validation on game load. JSON files are not validated on load, currently.
-5. Add block and item selection support. Should be easy enough with StAPI registries. I currently cannot think of a good use for this config option yet, though.
+5. Add block and item selection support. Should be easy enough with StAPI registries. I currently cannot think of a good use for this config option yet, though.

glass-config-api-v3/docs/Types.md

@@ -13,4 +13,4 @@ The built-in factories are as follows:
 - java.lang.Float[]
 - [java.lang.Enum](Using.md#enums)
 
-Should this list ever fall out of date, see [DefaultFactoryProvider.java](../blob/master/src/main/java/net/glasslauncher/mods/api/gcapi/impl/config/factory/DefaultFactoryProvider.java).
+Should this list ever fall out of date, see [DefaultFactoryProvider.java](../blob/master/src/main/java/net/glasslauncher/mods/api/gcapi/impl/config/factory/DefaultFactoryProvider.java).

glass-config-api-v3/docs/Using.md

@@ -59,4 +59,4 @@ Make your config category class, implement `GeneratedConfig`.
 
 - Use `GCAPI.reloadConfig` to manually set config values. This is to ensure mods are notified properly and can post-process things.
 - The config.json files are not sanitised or checked when loaded. This will be fixed in a later update once I figure out a good way to handle it. This is low on my list.
-- Servers are able to send whatever configs they want, so long as the config field on the client is MP syncable. The server doesn't even need to have the mod installed. This would require emulating GCAPI's config export code to do so, though. I'm not sure if I'll patch this. It seems like it would have its uses.
+- Servers are able to send whatever configs they want, so long as the config field on the client is MP syncable. The server doesn't even need to have the mod installed. This would require emulating GCAPI's config export code to do so, though. I'm not sure if I'll patch this. It seems like it would have its uses.