[
https://issues.apache.org/jira/browse/RAVE-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14076217#comment-14076217
]
Jmeas Pls commented on RAVE-1113:
---------------------------------
Of course. We will supply the community with documentation on any new API
endpoint, which will describe what it should return for each HTTP method, the
data it should contain, the structure of that data, and an example response.
Further, the mock API & data store will be around which will allow the
community to interact directly with those mock endpoints, which could also help
development of the real API.
> Create bootstrap API endpoint specification
> -------------------------------------------
>
> Key: RAVE-1113
> URL: https://issues.apache.org/jira/browse/RAVE-1113
> Project: Rave
> Issue Type: Sub-task
> Components: rave-portal
> Reporter: Jmeas Pls
>
> The Angular app will be entirely managed by, well, Angular. As with most
> client-heavy apps we will need a bootstrapping endpoint that gives all of the
> information necessary for Angular to build out the UI.
> Presently [our API|http://wiki.apache.org/rave/RESTAPI] is structured solely
> around the part of the app that manages gadgets. This isn't too surprising as
> that part of the app is where the bulk of the work on the Angular branch
> involves. But this bootstrapping route is just as important!
> In general, if the user isn't logged in then it might be as small as an
> object saying that they aren't authorized. If they are logged in, then it
> should be the user's info.
> This initial data will be sent back from the server with the initial request,
> as it's used during the app's startup.
> This task will be completed when:
> - The API specification for the Bootstrap route is complete
> - The client responds to an object on the window that represents the
> bootstrap object, redirecting you to login or the home page based on that
> object.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
