serversideup / roastandbrew Goto Github PK

In the Vuex module Users there is an error in one of the getters.

modules\users.js

getUserLoadStatus( state ){
return function(){
return state.userLoadStatus;
}
},

When I select one cafe entry from the list I see no details, look at this screenshot:

The app div just stays empty:

<div id="app">
 <router-view></router-view>
</div>

Your website validation regex is very explicit. It requires www. and disallows a trailing slash.

While not the end of the world, I spent more time than I would like to admit trying to figure out why I couldn't save a new café.

It seems to be canceled on role-permission table after the coding updated，I couldn't find admin
view, any other new design of roles？

I'm following your guide to develop a similar application. I am confused to how the City filter works. It doesn't seem like you are using the cafes that are passed through the API. Is it based on the city_id in on the cafe model?

Issue description

CORS error. Should we use a composer package to resolve or you have anything in your mind?

Environment

OS: Windows
Server: Apache
Node: v8.9.1
Npm: 6.1.0
Laravel 5.6

Environment

Laravel Homestead

Issue description

I tried to replace the socialite authentication with a passwordless medium style authentication.
First, the user provides his email where I send an authentication token (I replaced the social authentication links in the login modal with a form input for email );
Then, after clicking on the authentication link, the user is either created or retrieved by email and redirected to the home page.
In the authentication controller previously used for socialite, I check the token validity (existence and expiration ), and I log the user in with Auth::login($user) , $user being the user for the mail address the token came from.
I used Auth::login($user) by following the example for socialite authentication in roastandbrew code.

I also faced a bug related to the session storage file as described at laravel/framework#22514 that I bypassed by changing the session driver environment variable to cookie.

After redirecting the user, I noticed that despite the Auth::login($user) action I did, the user didn't appear as authenticated (userLoadStatus==3).

When I checked the API\UsersController.php, I saw that we get the authenticated user with Auth::guard('api')->user(), and I didn't understand why.

I thought that there would be something like Auth::guard('api')->login($user), but it throws an exception for non-existent method.

When I replace Auth::guard('api')->user() with response()->json(Auth::guard('api')->user()), the user appears to be logged in the application whereas a curl call with the following command :
curl -X GET -H 'Accept: application/json' http://memoire.local/api/v1/user returns an empty response.

dd(Auth::guard('api')->user()) throws an error when called from my token model dd(Auth::guard()->user()) does return a user.

I got confused, and after searching from yesterday, I decided to open this issue to know if I missed something.

By the way, your code is very fine and easy to understand, Thank you for it and the tutorial.

Steps to reproduce the issue

I mainly followed the steps in this medium article https://medium.com/@hive_adrian/password-less-email-authentication-in-laravel-ecf5388efe74 by adapting it to the single page app context (no blade view, response->json instead of views as return values, etc, ...)

Additional details / screenshots

I want to point out that my authentication routes were initially in the web.php but there was a 419 error which led me to write them inside the routes/api.php file.

Thank you very much !!

Issue description

Maybe a feature request, but neither filter page or cafe list page seem to support momentum scrolling which hurts the user experience on touch devices.

Environment

• What's My Browser Support link: < paste link here >
  Tested on iOS 12.1/Safari

Steps to reproduce the issue

1. Open webpage on touch device
2. Open filter or cafe list page
3. Try to scroll the page

What is expected?

A smooth flowing scroll motion using touch. Instead scrolling feels «sticky».

Link to where issue can be reproduced

Additional details / screenshots

Hello there !

Thanks for the amazing tutorial.

I was wondering if you already tried to fetch some resources through Passport to test some API routes and check if they are working correctly ?

Unfortunatly I can't manage to make it work even with the token in the "laravel_token" cookie, I'm always getting "Unauthenticated".

I'll get in touch by email once I'll have make this work, because I developed a proxy to protect the API for a SPA type of application on Laravel, and I've got some topics I would like to discuss with you.

thank you for the SPA. it's really helpful and also nice tutorial side.

I have a question about sign up option. I check out the live app and couldn't see the sign up option there. Do we need to add it by selves, is it possible to add it. Because if I understand it correctly you are deleting Laravel's auth option. also, changing the driver.

could you guide me about adding sign up in this app? thank you.

Hello again,

Any chance to have an upcoming tutorial on how to transform the WEB application to a Cordova mobile application ? This is taken from your first part of the tutorial :

So in this article series, we will start by setting up a web app that allows for a consumable API in the back end and authentication with social providers. We will then move to a mobile app using Cordova and the same components we used. The app will be an SPA on the web side and the mobile side. When the web side is complete there should be very little configuration to transfer the app using the same components, styles, and structure to turn it into a mobile app. Of course there are a few tweaks that should be made, but we should be able to isolate those easily. This will allow for simultaneous development that’s easily transferred between web and mobile.

Thanks in advance !

When I tried to edit a cafe to upload a photo It's not working and after some investigation I figured out it's related to PUT method and multipart/form-data so I added:
formData.append('_method', 'PUT')
to putEditCafe in api/cafe.js and changed axios method from put to post so the problem solved in this way.