Can I have a front-end page/endpoing that is not reflecting api?

[mikaelhm]

I wanted to make a login page at /login, that I can redirect to whenever someone is not logged in.

I created a template front/login/getIndex.jade and setup the angularjs routes:

  .when('/login', {
    templateUrl: '/html/login/getIndex.html',
    controller: 'login'
  });

If I try to hit /login i get a 404. However, if I link to /login from within angularjs it works.

I then realized that the 404 was caused by the fact that I did not have a getIndex request handler defined in back/login. The server should properly log some error message in this case!

But, wouldn't it be nice to be able to have endpoints that does not require back-end data?

[JonAbrams]

Yup, the reverse would also be good, an API GET endpoint without an
associated view.

For now though, I'd just use express to create the endpoint you require in
back-app.js

On Thu, Aug 14, 2014 at 9:11 AM, Mikael Møller notifications@github.com
wrote:

I wanted to make a login page at /login, that I can redirect to whenever
someone is not logged in.

I created a template front/login/getIndex.jade and setup the angularjs
routes:

.when('/login', {
templateUrl: '/html/login/getIndex.html',
controller: 'login'
});

If I try to hit /login i get a 404. However, if I link to /login from
within angularjs it works.

I then realized that the 404 was caused by the fact that I did not have a
getIndex request handler defined in back/login. The server should
properly log some error message in this case!

But, wouldn't it be nice to be able to have endpoints that does not
require back-end data?

—
Reply to this email directly or view it on GitHub
#68.

[mikaelhm]

Yup, the reverse would also be good, an API GET endpoint without an
associated view.

Doesn't that work already?

[JonAbrams]

Nope, it makes a view endpoint for all GET API handlers:
https://github.com/JonAbrams/synth/blob/master/synth.js#L121

On Thu, Aug 14, 2014 at 9:18 AM, Mikael Møller notifications@github.com
wrote:

Yup, the reverse would also be good, an API GET endpoint without an
associated view.

Doesn't that work already?

—
Reply to this email directly or view it on GitHub
#68 (comment).