REST-API: vagueness/issues in specification
This is a collection of vagueness and issues of the REST API specification:
- It is unclear how exactly the depth parameter should behave, or more precisely, which effect the possible values
resolveshould have on the returned object.
- The AAS respository interface lacks specification.
- The response format is not specified for routes
- Does the parameter
identification.idcontain the whole
identificationobject or just the id attribute? Or does it work like a str in str filter?
- Syntax and semantics are unspecified for parameter
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information