Import/export runtime information from graph JSON

[th0br0]

Runtime information can be imported from gists (i.e. https://gist.github.com/th0br0/c906d736ae732190c46e), however, it is not serialised when manually exporting a graph.

Is this intended behaviour?

[jonnor]

Is everything under properties top-level key missing?
Does this happen only when the graph was imported from gist, or also for graphs created manually?

It is probably not intended behavior.

[th0br0]

properties is populated as follows for a manually created graph. It might be related to #488 though.

 "properties": {
        "name": "main",
        "id": "test/main",
        "project": "test",
        "environment": {
            "type": "noflo-browser"
        },
        "changed": true
    },

[jonnor]

And when importing from a gist it looks like?

[th0br0]

Assuming that

    "properties": {
        "name": "ttttt",
        "environment": {
            "type": "noflo-browser",
            "protocol": "iframe",
            "address": "http://th0kus.ngrok.io/everything.html"
        }
    },

is a valid header properties header for an imported gist, it'd seem that my tests earlier got a bit screwed up. It seems that the runtime isn't imported from the gist at all!?

[jonnor]

I don't think protocol and address are recognized attributes under environment? But it would be very useful to have something to allow specifying custom runtime in graph. CC @bergie

[th0br0]

Well, I tried out various combinations, including {"type":"html","src":"http://...","protocol":"iframe"} to no avail. And the official graph-schema.json doesn't specifcy the properties contents... where'd be a better place to look?

[jonnor]

There is probably no place better :) We should update it!

Anyway, rephrasing the issue as an enhancement request to load runtime information (protocol, address) from imported graphs (at least gists), and to export the information to .json. Do you agree with that?

[th0br0]

Yes - that'd be awesome!

On Mon, Aug 10, 2015 at 1:12 PM, Jon Nordby [email protected]
wrote:

There is probably no place better :) We should update it!

Anyway, rephrasing the issue as an enhancement request to load runtime
information (protocol, address) from imported graphs (at least gists), and
to export the information to .json. Do you agree with that?

—
Reply to this email directly or view it on GitHub
#487 (comment).