-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[API] Schemata containing simple types cannot be retrieved via the API #98
Comments
Findings so far:
|
@pflueras Thanks, it does not hang anymore, thats certainly an improvement. However, simple types other than To reproduce, please have a look at #101, it contains both unit and e2e tests showing the issue. In In Please feel free to work in the |
@wwerner My intention was for the Spec: becomes: The above supports plain types, in case standard types not desired/used. Further, if using a standard base class, spec should be: becomes:
Sorry for the surprise |
…at first, sorry This reverts commit ff32040.
This is not fixed yet. I opened a new branch containing tests to reproduce, as the original one was merged already. I ignore the failing tests on master now and work on the issue in #115 |
This issue is likely to be fixed fixed by #117 |
When requesting the sources for a schema that contains at least one basic type not checked for in
io.vlingo.schemata.codegen.processor.types.ComputableTypeProcessor#resolveType
, the request hangs.Schema not containing simple types can be retrieved, but after trying to retrieve one that does, a second try with a schema that worked before also fails.
If I'm not mistaken, this only happens with the
TypeResolver
inSchemaVersionQueriesActor
,CacheTypeResolver
did work with basic types.When compiling the same schema within a test, the compilation works.
To reproduce via the http API:
src/test/resources/rest-api-calls.http
starting fromL:148
one after anotherL:160
) leads to the issueTo reproduce via the UI:
string
property, see exampleSource
Minimal example spec:
There already was a discussion on Slack, but I prefer having an issue to reference instead of searching within the chat history.
The text was updated successfully, but these errors were encountered: