Export to json

medini_1061617127

 Hello Medini Team,

I wrote a javascript to export requirements from Medini to json.

Now I want to export all type of profiles and challenge different output problems:

- string property designdecision writes "null" instead of "" if field is blank

- kind and state property writes info block ("empty: false, "blank...)

- dateproperty writes number output

- richtextproperty writes font info

- relatedgoals shows syntax error

- referenceproperty shows script error

Here is a short version of the code. Can you please help me to correctly access the metamodel properties?

Many thanks in advance,

Daniel

medini_1024169437

Hi Daniel,

I am not 100% sure about the problems but I took your script and reduced it basically to this small snippet:

var sample = {
 name: null,
 id: undefined,
 description: new java.lang.String("looooong description with \n line break"),
 booleanproperty: java.lang.Boolean.FALSE,
};

console.log("{0}", JSON.stringify(sample, null, 2));

That gives a a set of strange looking output as JSON is not good in dealing with Java objects.

In my tets it looks like this:

{
 "name": null,
 "description": {
 "empty": false,
 "blank": false,
 "bytes": {
 "0": 108,
 "1": 111,
 "2": 111,
 "3": 111,
...
 "32": 32,
 "33": 98,
 "34": 114,
 "35": 101,
 "36": 97,
 "37": 107
 }
 },
 "booleanproperty": {}
}

I see several ideas to improve, first one is to tweak the way you write data to the object a bit like this sample explains:

var x = null;
var y = java.lang.Boolean.TRUE;

sample = {
 name: x ? x : "",
 id: undefined,
 description: '' + new java.lang.String("looooong description with \n line break"),
 booleanproperty: y ? true : false,
};

console.log("{0}", JSON.stringify(sample, null, 2));

Output is now much better:

{
 "name": "",
 "description": "looooong description with \n line break",
 "booleanproperty": true
}

So basically: 

- check if a string or boolean is defined yourself and use the right defaults

- combine '' with the string to make sure its a JS string

- use undefined and not null

Other idea is to use uneval() and not JSON.stringify, it works a but different. In helper.js I once started to hack an unevalEx to cope with Java object issues, maybe you have  alook to that too.

Happy Scripting

Jan