Null value after config update about okaeri-configs HOT 7 CLOSED

Please make sure a default constructor is available. Otherwise, okaeri-configs can in some cases create the instance with unsafe which does not fill default values.

from okaeri-configs.

What do you mean by default constructor?

from okaeri-configs.

A default constructor is a constructor which can be called with no arguments (either defined with an empty parameter list, or with default arguments provided for every parameter).

This can be also achieved using @NoArgsConstructor from Lombok.

from okaeri-configs.

I tried this way but there is still a null value.

from okaeri-configs.

Please provide specific instructions where and what to add to reproduce the problem, as your configuration has multiple levels.

from okaeri-configs.

These variables are already added to the PluginConfiguration.java file so you just have to run the creator to see newly added null values. On line 168 you have that 2 last constructor params that are null values when you try to update the config with provided ConfigManager creator. This built-in MySQL class that produces null values is initialized on line 149.

from okaeri-configs.

That explains a bit. Please use fields for the default values, instead of the full constructor for the subconfig initialization, if you want okaeri-configs to add the new default values.

// don't
public MySQL mysql = new MySQL("localhost", 3306 /* ... */);
// do
public String hostname = "localhost";
public int port = 3306;
// ...

Note that this behavior is indeed correct, because you are only providing the default value for the mysql itself, which is, in fact, already present when adding properties to the MySQL class.

from okaeri-configs.