we may need a jsonType to determine if array or object

[toddgeist]

Not adding yet. But I do have this code already in a couple of functions. It might be useful to be able to walk JSON with FileMaker Scripts.

[dansmith65]

I assume this is just...

Let (
    ~firstAndLast = Left ( json ; 1 ) & Right ( json ; 1 )
    Case (
        ~firstAndLast = "{}" ;
        "object" ;

        ~firstAndLast = "[]" ;
        "array" ;

        "unknown"
    )
)

Is a function really necessary for this?

[toddgeist]

The above function would return "unknown" in the case of valid json string with either leading or trailing white space.

The other json functions all handle whiteSpace, so do the BE_JSON functions

[toddgeist]

the better point might be that some of the jsonFunctions have the code to properly determine type ignoring all white space. It might be good to expose that logic so that if its required you can use the same logic.

[dansmith65]

Good point. I figured my example code would work for json returned from the jsonGet CF, which I would expect to be the most common use-case, but it's probably better to handle whitespace. Having a CF also makes the code read nicely.

Should it also detect "string", "number", and "boolean"?

[toddgeist]

I thought about other data types, and I think there might be a case there. But I am unsure how long it would take to add support for all the other types. So I just punted for now. You may have a better idea since the #functions handle data types.

A related issue is how to handle dates and times from from the jsonGet() function. I don't think there is standard so I thought we would have to a fmqboCF that handles formatting back and forth between FM and qbo.

[dansmith65]

I was only suggesting we detect JSON data types, so that wouldn't include date, time, or timestamp. I think your suggestion of an fmqbo namespaced custom function to convert from the timestamp used by QBO is best. Here is the list of JSON "data types" as I called them, but should probably be referred to as values:

• string
• number
• object
• array
• true
• false
• null

[dansmith65]

For what it's worth: if this function existed, I would have just used it in my tests file to confirm that the isSandbox boolean value existed and contained a boolean value.

[toddgeist]

I might need this same logic again to fix #22