exceptions are not exposed on Services/Functions

[blampe]

exception Foo {}

service Bar {
    string baz(
     ) throws (
         1: Foo err,
     );
}

I'd expect to be able to reference service.Bar.Foo or service.Bar.baz.Foo.

cc @kriskowal

[Torwegia]

This is also true for structs or anything else defined outside of the service definition. It leads to service.module.X which is unfortunate.

[kriskowal]

For cross-reference, in ThriftRW-node you get:

• thrift.Foo
• thrift.Bar
• thrift.Bar.baz.Arguments
• thrift.Bar.baz.Result

And the expectation is to carry the thrift object around.

[kriskowal]

…of course, with ThriftRW-node, you can duck-type all these with plain old objects so nobody knows about this structure yet.

[abhinav]

With thriftrw, service is a module which exports all the types and and service.Bar is just a simple object that exposes objects representing the service methods.

I guess it'll be easier for people coming from Apache Thrift if we re-exported all types as attributes in service.Bar (re-exporting just the things used by the service is probably more book-keeping than it's worth).

[blampe]

I would make migration a little easier. Also we could eventually do smart things, like not allow service.Bar.SomeException if Bar doesn't declare SomeException as something it throws.