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
Importing a JSON file does not let Minerva know what data type is preferred for integer values. It appears to assign them all to the "Number" data type by default.
I would suggest either some kind of "meta data" included in the exported JSON which specifies data types, or a way to have the program automatically decide on importation.
Additionally, some kind of scripting interface so that this kind of thing could be automated by users would be nice, but it appears that the entire program is encapsulated in an anonymous function right now.
The text was updated successfully, but these errors were encountered:
This would be very far down the road if I did do this. Minerva is made to service a dying technology and it's a side-project. To build a scripting API to automate this is a bit beyond the scope of what minerva was made to do. I can look into passing data type metadata, but again, a bit back burner, atleast for now.
Importing a JSON file does not let Minerva know what data type is preferred for integer values. It appears to assign them all to the "Number" data type by default.
I would suggest either some kind of "meta data" included in the exported JSON which specifies data types, or a way to have the program automatically decide on importation.
Additionally, some kind of scripting interface so that this kind of thing could be automated by users would be nice, but it appears that the entire program is encapsulated in an anonymous function right now.
The text was updated successfully, but these errors were encountered: