Describe the bug
When editing entries for weapons or systems part of licenses, certain fields that are meant to only accept numbers (i.e. License Level, Ranges) get translated into strings. This causes issues when imported into COMP/CON, and can cause various weapon or system entries to fail to appear if a license level is entered using the keyboard instead of when its increased or decreased with the Spin Button controls.
To Reproduce
Steps to reproduce the behavior:
Go to Manufacturers and Licenses and add a new System, Weapon, or Mod.
While entering the information, click on the License Level field and type in a number.
Export the weapons/system/mods.json component of the LCP & open it in a text editor
See that the number entered is in quotes.
Expected behavior
Fields such as this should always convert the value to numbers, even when typed in. Otherwise, license components can fail to appear in the appropriate sections when viewing them in the compendium or when choosing licenses in COMP/CON.
Screenshots
An added example of "Range" not being parseable from a string causing the entire Mech Weapons compendium to fail to list:
Describe the bug When editing entries for weapons or systems part of licenses, certain fields that are meant to only accept numbers (i.e. License Level, Ranges) get translated into strings. This causes issues when imported into COMP/CON, and can cause various weapon or system entries to fail to appear if a license level is entered using the keyboard instead of when its increased or decreased with the Spin Button controls.
To Reproduce Steps to reproduce the behavior:
Expected behavior Fields such as this should always convert the value to numbers, even when typed in. Otherwise, license components can fail to appear in the appropriate sections when viewing them in the compendium or when choosing licenses in COMP/CON.
Screenshots
An added example of "Range" not being parseable from a string causing the entire Mech Weapons compendium to fail to list: