Proposal: Automatic <property> type discovery based on value
-
Proposal:
(1) Ignore nodes:
<boolean/>,<number/>and<string/>, instead always infer them from thevalueattribute of apropertynode.
(2) Add optional attributes to<property>:- min | number | default
null - max | number | default
null
Background
The game engine today already tries to infer the value of a property based on the value type when the value type tag is not specified. But, the engine will not infer 'boolean' types, only 'string' and 'number' types. In this proposal we would change the code to always do type inference in addition to automatically inferring 'boolean' types.
Example, Before:
<propertyList> <property name="Projection of Power" value="false"> <boolean/> </property> <property name="neutralCharge" value="0"> <number min="1" max="10000"/> </property> <property name="mapName" value="world_at_war"> <string/> </property> </propertyList>Example, after:
<propertyList> <property name="Projection of Power" value="false"/> <property name="neutralCharge" value="0" min="1" max="10000"/> <property name="mapName" value="world_at_war" /> </propertyList> - min | number | default
-
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login