Skip to content
This repository has been archived by the owner on Mar 18, 2021. It is now read-only.

OpenAPI generation broken at Enum #655

Closed
ewoudje opened this issue Apr 13, 2019 · 4 comments · Fixed by #658
Closed

OpenAPI generation broken at Enum #655

ewoudje opened this issue Apr 13, 2019 · 4 comments · Fixed by #658

Comments

@ewoudje
Copy link

ewoudje commented Apr 13, 2019

There is something wrong in my code when i do aqueduct document it fails with this:

-- Aqueduct CLI Version: 3.2.0+1
-- Aqueduct project version: 3.2.0+1
*** Uncaught error
    Bad state: Invalid argument(s): Illegal argument in isolate message : (object is a regular Dart Instance)
  **** Stacktrace
  * #0      _SendPortImpl._sendInternal (dart:isolate/runtime/libisolate_patch.dart:218:70)
  * #1      _SendPortImpl.send (dart:isolate/runtime/libisolate_patch.dart:202:5)
  * #2      main (<data:application/dart>:13:12)
  * <asynchronous suspension>
  * #3      _startIsolate.<anonymous closure> (dart:isolate/runtime/libisolate_patch.dart:296:32)
  * #4      _RawReceivePortImpl._handleMessage (dart:isolate/runtime/libisolate_patch.dart:171:12)
  ****

But aqueduct serve does work and i tried a sample project and there aqueduct document does work. https://github.com/ewoudje/rulers_of_states/tree/master/server

@ewoudje
Copy link
Author

ewoudje commented Apr 13, 2019

I've found the source from the error it was an enum in a ManagedObject. Is this expected behavior? I thought it was allowed for an enum?

@ewoudje ewoudje changed the title OpenAPI generation broken at Serializable OpenAPI generation broken at Enum Apr 13, 2019
@itsjoeconway
Copy link
Contributor

Yes, there is a bug with enums. It will be fixed in 3.2.1

@pretorean
Copy link

I also got with the same error. Good thing you fixed it. Waiting for release.

@itsjoeconway
Copy link
Contributor

3.2.1 release is now available on pub.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants