[
https://issues.apache.org/jira/browse/UNOMI-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Serge Huber updated UNOMI-180:
------------------------------
Description:
We should implement the CXS specification, as we are supposed to. The
specification has now switched from REST API to GraphQL API, so the work will
begin on implementing GraphQL in a separate branch.
Basically we are implementing the specification that is tracked here :
[https://github.com/sergehuber/contextserver-graphql-api/blob/master/javascript/cxs-graphql-schema.js]
The idea is to implement this API on top of the existing data and structure
already inside Apache Unomi. Some model adjustements might be needed but the
goal is to keep the REST API compatible. Hopefully this will be possible :)
was:We should implement the CXS specification, as we are supposed to. The
specification has now switched from REST API to GraphQL API, so the work will
begin on implementing GraphQL in a separate branch.
> Implement CXS GraphQL specification
> -----------------------------------
>
> Key: UNOMI-180
> URL: https://issues.apache.org/jira/browse/UNOMI-180
> Project: Apache Unomi
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.3.0-incubating
> Reporter: Serge Huber
> Priority: Major
> Fix For: 2.0.0-incubating
>
>
> We should implement the CXS specification, as we are supposed to. The
> specification has now switched from REST API to GraphQL API, so the work will
> begin on implementing GraphQL in a separate branch.
> Basically we are implementing the specification that is tracked here :
> [https://github.com/sergehuber/contextserver-graphql-api/blob/master/javascript/cxs-graphql-schema.js]
> The idea is to implement this API on top of the existing data and structure
> already inside Apache Unomi. Some model adjustements might be needed but the
> goal is to keep the REST API compatible. Hopefully this will be possible :)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
