JSON Import of License Fails When Boolean Values Are Provided as Strings

[Vaibhavsahu2810]

Description

When importing licenses via the /api/v1/licenses/import endpoint, the system currently fails if boolean fields ("marydone") are provided as strings in the JSON file. This results in a 500 error with the message:

{
  "status": 500,
  "message": "invalid json",
  "error": "json: cannot unmarshal string into Go struct field LicenseDB.marydone of type bool",
  "path": "/api/v1/licenses/import",
  "timestamp": "2025-03-24T12:30:15+05:30"
}

Steps to Reproduce

1. Use licenseRef.json containing license data with "marydone": "f" (as a string)
2. Submit this file to the import endpoint
3. Observe the 500 error response

Expected Behavior

The API should handle string representations of boolean values and convert them appropriately using parseBool function.

[Vaibhavsahu2810]

Hey @GMishx @deo002 , Could you please confirm if this expected behavior is intended?

[GMishx]

Yes it is. {"marydone": "f"}cannot be translated to a boolean. The import endpoint is intended to import JSON exported by the project, not licensesRef. It has to be passed as a special flag while running the application.

[Vaibhavsahu2810]

@GMishx Thanks for the clarification sir! Actually i know that current implementation is correct what i am asking was should we handle this specific scenario or not... So , now according to you we can add specific flag,If the flag (e.g., parsebool) is set, the importLicense function will first preprocess the JSON which converts converts "t" → true and "f" → false before decoding, If the flag is not set, the import will reject improperly formatted JSON as it does now, Am i right or missing something ??

[GMishx]

There is already -datafile flag for it. There is no need to parse t as true as it will break imports of JSON exported by laas.