You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The output model.json generated by importing api specs using sysl is a non-determinstic function of the input.
Running a command line sysl pb --mode json --root . specs/spec.sysl --output model.json on the same input API spec again and again can produce different output model.json files
instances where we have seen non-deterministic output in model.json
Description
The output model.json generated by importing api specs using sysl is a non-determinstic function of the input.
Running a command line
sysl pb --mode json --root . specs/spec.sysl --output model.json
on the same input API spec again and again can produce different outputmodel.json
filesinstances where we have seen non-deterministic output in
model.json
calls to REST endpoints defined in open api specs where the spec defines multiple possible content-types for the request body. Sysl-go importer appears to arbitrarily pick one of the content-types to write to the output
model.json
. Issue isolated and logged as sysl openapi spec importer behaviour is nondeterministic if input open api spec defines multiple request bodies with differing content-types #1058Sysl-go importer regards schemas of query parameters as fungible between different endpoints with different schemas in some cases where the query parameters have the same name. This is wrong as well as producing nondeterministic behaviour. Issue logged as sysl openapi spec importer behaviour assumes query params of different endpoints with the same name have the same schema, and non-deterministically picks a schema for them both to use #1059
steps to reproduce
see individual linked issues above
Expected behavior
importer is determinstic
Actual behavior
importer is not deterministic
The text was updated successfully, but these errors were encountered: