stuartmorgan-g
stuartmorgan-g
> It's just that the objc/swift side uses `FlutterError`, so I was just trying to follow the same convention. `FlutterError` is explicitly intended for returning errors over platform channels from...
In Java values are returned using [Result](https://github.com/flutter/engine/blob/main/shell/platform/android/io/flutter/plugin/common/MethodChannel.java#L194). Everything is async in the engine APIs. The reason things are more complicated in Pigeon is that it provides a convenience system for...
It's unfortunate to make error handling slightly different in every plugin in Kotlin just for that rare case. What about a `KotlinOptions` entry to allow overriding the generated error class...
> By default, the error class name for kotlin is derived from the file name Why? My suggestion was that we have the default (which is all that the I...
> To prevent developer error here, I think it would be useful to have some mechanism to make the created interface have callbacks of type `Result`. I'm not sure what...
> I would expect this to be the standard for how errors should look like when coming from the native side. But this is currently not the case for any...
Closing as obsolete; it's now at 2.18.4 on master.
Some other Pigeon PRs landed; could you re-rev the version here?
@hangyujin What's the status of this PR? Are you planning on updating it based on the discussion above?
@chunhtai What's the status of this PR? It looks like it's probably waiting for another review.