-
Notifications
You must be signed in to change notification settings - Fork 1
Error Messages
A248 edited this page Dec 1, 2021
·
5 revisions
Loading a configuration can fail for various reasons.
This page is deprecated. Error codes have been moved into DazzleConf itself. This page is left because it is referenced by a handful of snapshot builds of DazzleConf.
These are thrown with IllDefinedConfigException. Software developers are responsible for fixing them.
- D1A, D1B, D1C
- D1A - The in-progress configuration data contained a plain object where a configuration section was expected.
- D1B – One configuration object replaced another.
- D1C – The loaded configuration data contained a plain object where a configuration section was expected.
- These all happen when you mix plain config entries with configuration sections in a way which doesn't make sense. Consider this example. The keys of the entries conflict with each other. It isn't possible for "keyOne" to be both a configuration section and a string value at the same time.
@ConfKey("keyOne")
@ConfDefault.DefaultString("some")
String string();
@ConfKey("keyOne.subKey")
@ConfDefault.DefaultString("other")
String otherString();