You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My plan is to create new DataType API so plugins are able to register and utilize their own DataTypes without being forced to use one of the preexisting.
I'm also planning on changing the DataType Enum to an object. So instead of enums, the DataType's will be constants. We'll then grab all the constants via reflection and add them into the table. Enums are incredibly limiting and should only be used for really basic things like ID constants.
Basic rundown:
Register your DataType before it's used. The method may be DataType.addDataType(customDataType);
The DataType consists of a view variables such as the name, and the ID. You will NOT be able to define a custom constructor due to the fact that the constructor is used specifically by the HawkEye query and modifying the constructor will cause exceptions. So instead you'll define your DataEntry class (Whether it's custom, or one of HawkEye's).
I will MOST LIKELY expand the DataType's further to allow for better ingegration with the web interface. For instance, being able to define whether or not a DataType is serialized as a block, or item.
If a DataType is registered with a pre-existing ID, or too large of an ID, an exception will be thrown. Same goes for having the same name as a DataType.
Once the DataType is registered, it'll be entered into the MySQL. This is so the webinterface can see the new datatypes. It's also so if a custom datatype is registered once, and then not registered the next runtime, we can simply create a dummy DataType instead of returning a null DataType. Registering your DataType replaces the Dummy value.
The text was updated successfully, but these errors were encountered:
My plan is to create new DataType API so plugins are able to register and utilize their own DataTypes without being forced to use one of the preexisting.
I'm also planning on changing the DataType Enum to an object. So instead of enums, the DataType's will be constants. We'll then grab all the constants via reflection and add them into the table. Enums are incredibly limiting and should only be used for really basic things like ID constants.
Basic rundown:
Register your DataType before it's used. The method may be DataType.addDataType(customDataType);
The DataType consists of a view variables such as the name, and the ID. You will NOT be able to define a custom constructor due to the fact that the constructor is used specifically by the HawkEye query and modifying the constructor will cause exceptions. So instead you'll define your DataEntry class (Whether it's custom, or one of HawkEye's).
I will MOST LIKELY expand the DataType's further to allow for better ingegration with the web interface. For instance, being able to define whether or not a DataType is serialized as a block, or item.
If a DataType is registered with a pre-existing ID, or too large of an ID, an exception will be thrown. Same goes for having the same name as a DataType.
Once the DataType is registered, it'll be entered into the MySQL. This is so the webinterface can see the new datatypes. It's also so if a custom datatype is registered once, and then not registered the next runtime, we can simply create a dummy DataType instead of returning a null DataType. Registering your DataType replaces the Dummy value.
The text was updated successfully, but these errors were encountered: