Register action
Closed this issue · 8 comments
I can not seem to get the register action to work. Is the register action on master currently in a working state?
Btw, I have created an example API server using rails and devise:
I have found it helpful to use this example when playing around with ember auth easy, and I hope it may be of use to others as well.
I have an example ember client that demonstrates the problem here:
Clicking the register link does not trigger any action.
Thank you so much for your pull request and issues! I will take a look tomorrow.
Thank you for making Ember Auth Easy and your offer of assistance. :)
Still ugly visually, but should work now. Thanks for catching that.
Thanks!
The register action acts as if it was successful on my example client and server, but it does not make any network calls to the api server.
I am debugging this using my example token api server (https://github.com/digitalplaywright/rails-devise-token-server) together with my example ember app kit client with ember auth easy (https://github.com/digitalplaywright/ember-appkit-with-ember-auth-easy/tree/ember-auth - ember auth branch).
Is the registration action sending a request to the server for you? And if so, can you see what I am doing wrong? The only think I can think of is a CORS issue, but as far as I can see the server is using rack-cors correctly and no error is reported.
Correct me if I'm wrong, but your server (ember-appkit-with-ember-auth-easy) appears to be using the FixtureAdapter, so it won't send anything to the server.
I had the same desire as you to setup example clients and servers to test this. I have them setup, using a new library I wrote for this purpose that makes managing them easy. They work both in serverless/fixture mode, and in true client server mode. I have to run right now, but I'll put up a description of how to get and use them later tonight or tomorrow morning. After that I'd love to get your feedback.
If you wanted to try before I can get a writeup up, the short version:
For the client: run rake overlay:build in the EAE root. This will build an app in test_overlay_app. Run it on port 9600.
For the server: run rake test_server:build in the EAE root. This will build a rails server in test_server. Run it on port 5901.
Based on Murphy's Law, there's a 99% chance there will be a snag somewhere in the process and it won't work for you without a single hiccup, given that I just "finished" it an hour ago. But there's always a chance.
Sounds good. I will wait until you have the writeup so that I can help find potential problems.