Hi guys,
Jan and I worked today on the CXS REST API and here is a quite summary of what we did:
- Merged the pull request #6
- Added a comment on pull request #5 and didn't merge it because the EBNF grammar file was created by Chris before we decided to focus on a JSON only query format. My suggestion would be that we remove this file to avoid any further confusion.
- We then worked some more on the profiles endpoint, decided that for the profile creation we would specify a profile body JSON structure that didn't contain an ID, and if it did it would simply be ignored and the server would generate a new ID.
- On the profile query endpoint, we discussed the changes made by Thomas to move the pageSize and offset into the the request body, but concluded that this was ok since we had to submit the query at each request every time, even for simple page navigation.
- We also started working on the aggregations in the QueryResult, mostly using ElasticSearch as a source of inspiration, please have a look at our changes to see if this is similar to what you expected. We also thought that aggregations, despite the added complexity they introduce, would be very useful for this API.
That's all folks,
cheers,
Serge...
Serge Huber
CTO & Co-Founder
T +41 22 361 3424
9 route des Jeunes | 1227 Acacias | Switzerland
> JOIN OUR COMMUNITY to evaluate, get trained and to discover why Jahia is a leading User Experience Platform (UXP) for Digital Transformation.