rave-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jmeas Pls (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (RAVE-1113) Create bootstrap API endpoint specification
Date Mon, 21 Jul 2014 19:26:39 GMT

     [ https://issues.apache.org/jira/browse/RAVE-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jmeas Pls updated RAVE-1113:
----------------------------

    Description: 
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.

  was:
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.


> Create bootstrap API endpoint specification
> -------------------------------------------
>
>                 Key: RAVE-1113
>                 URL: https://issues.apache.org/jira/browse/RAVE-1113
>             Project: Rave
>          Issue Type: 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)

Mime
View raw message