If the API name is the same as the schema object name, then Streamy generates two classes with the same name

[gsadams]

I've just used Streamy to generate the code to talk to the Google Calendar API.

https://www.googleapis.com/discovery/v1/apis/calendar/v3/rest

The API is called Calendar, and the schema object is also called Calendar. So, I end up with generated code including:

class Calendar extends base.EntityWrapper {
....
}

class Calendar extends base.Root {
...
}

As you can imagine, this causes unhappiness when the Streamy API layer is used.

[alxhub]

Fixed.

Addendum data now allows overriding the top-level class name, via the 'topLevelClassName' key of the addendum document.