Comments on Extensible API for accessing structured data
Last modified by Vincent Massol on 2024/02/26 17:51
Choose the export format from the list below:
Export as Portable Document Format (PDF) using the Web Browser
Export as HyperText Markup Language (HTML)
We should also provide:
application.getCurrentItem which would return item associated to the current document if the document is an item of the application.
I believe offset and limit should be mandatory.
That is a proposition of Vincent that every XWiki API must be ready to scale well.
Having a getItems() with no limit could be very costly if you have a lot of items.
Why .data? Can't it be $movie.name?
Agreed, this came from the original from fabio, secondarily Ludovic mentioned that we should implement both xwql and hql in getItems()
We should also consider how to display data, aka $obj.display() (view) using this api, we should have the data necessary to do display() (edit), maybe this should be part of getSchema(). We should consider building todomvc.com application using this api so we know it works as we design it. The concern is that we have drop-down menus based on static lists and DBlists but we are not currently talking about display/edit of them. Refer to the Task Manager Application app.
Updated the document to replace $movie.data.name with $movie.name