Fixing #74.

[lleadbet]

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Problem/Feature

Fixes #74; the append function was nesting the array as the data type comes in as an interface{} vs. the real []interface{}

Description of Changes:

• Fixes Nested arrays in API responses #74

Checklist

• My code follows the Contribution Guide
• I have self-reviewed the changes being requested
• I have made comments on pieces of code that may be difficult to understand for other editors
• I have updated the documentation (if applicable)

[zneix]

Just curious, why do we omit this in case of "schedule"?

[lleadbet]

Just curious, why do we omit this in case of "schedule"?

Schedule APIs don't have the data in the data value, instead it's under a nested segments value. Because of this, they're not an array of interfaces, just a regular interface and it'll panic.

[zneix]

Just curious, why do we omit this in case of "schedule"?

Schedule APIs don't have the data in the data value, instead it's under a nested segments value. Because of this, they're not an array of interfaces, just a regular interface and it'll panic.

Right, I forgot that's the case. Thank you for quick response!