-
Notifications
You must be signed in to change notification settings - Fork 230
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
CloudEvents route follow up tasks #903
Comments
ctron
added a commit
to ctron/ditto
that referenced
this issue
Dec 4, 2020
This change allows to make the schema optional and also allows to configure the data content type. Signed-off-by: Jens Reimann <[email protected]>
ctron
added a commit
to ctron/ditto
that referenced
this issue
Dec 4, 2020
This change allows to make the schema optional and also allows to configure the data content type. Signed-off-by: Jens Reimann <[email protected]>
ctron
added a commit
to ctron/ditto
that referenced
this issue
Dec 4, 2020
This change allows to make the schema optional and also allows to configure the data content type. Signed-off-by: Jens Reimann <[email protected]>
ctron
added a commit
to ctron/ditto
that referenced
this issue
Dec 4, 2020
This change allows to make the schema optional and also allows to configure the data content type. Signed-off-by: Jens Reimann <[email protected]>
I created PR #905 … following up in content-type suffix , optional data schema and additional content type. |
ctron
added a commit
to ctron/ditto
that referenced
this issue
Dec 4, 2020
This change allows to make the schema optional and also allows to configure the data content type. Signed-off-by: Jens Reimann <[email protected]>
ctron
added a commit
to ctron/ditto
that referenced
this issue
Dec 8, 2020
This change allows to make the schema optional and also allows to configure the data content type. Signed-off-by: Jens Reimann <[email protected]>
ctron
added a commit
to ctron/ditto
that referenced
this issue
Dec 9, 2020
This change allows to make the schema optional and also allows to configure the data content type. Signed-off-by: Jens Reimann <[email protected]>
ctron
added a commit
to ctron/ditto
that referenced
this issue
Dec 9, 2020
This change allows to make the schema optional and also allows to configure the data content type. Signed-off-by: Jens Reimann <[email protected]>
ctron
added a commit
to ctron/ditto
that referenced
this issue
Dec 9, 2020
This change allows to make the schema optional and also allows to configure the data content type. Signed-off-by: Jens Reimann <[email protected]>
thjaeckle
added a commit
that referenced
this issue
Dec 9, 2020
[#903]: Make schema optional, allow alternate content type
thjaeckle
added a commit
to bosch-io/ditto
that referenced
this issue
Dec 10, 2020
… API 2 Signed-off-by: Thomas Jaeckle <[email protected]>
thjaeckle
added a commit
to bosch-io/ditto
that referenced
this issue
Dec 10, 2020
* missing specversion lead to 500 error * exception texts were improved Signed-off-by: Thomas Jaeckle <[email protected]>
thjaeckle
added a commit
that referenced
this issue
Dec 10, 2020
[#903] provide OpenAPI documentation for /cloudevents on API 2
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After the first part of adding a
/cloudevents
route done in #889 and PR #895 there are some follow ups:application/json
content-type, also accept the Ditto Protocol content typeapplication/vnd.eclipse.ditto+json
([#903]: Make schema optional, allow alternate content type #905)ce-dataschema
optional - but if it is provided, it must start withditto:
([#903]: Make schema optional, allow alternate content type #905)/cloudevents
route and providing the Ditto Protocol JSON schema inline in the OpenAPI doc ([#903] provide OpenAPI documentation for /cloudevents on API 2 #911)The text was updated successfully, but these errors were encountered: