Fetching Laravel

Jerguš Lejko — Thu, 09 Nov 2017 00:00:00 +0000

What? Last night, shamelessly enough, I spent about 3 hours figuring this out. I was working on a Laravel site that has a concept of “companies”. The companies.index view simply lists all companies in the database (no pagination). I wanted to add a search functionality that would update the HTML table as the user types in the query.

Issue

When I was sending an AJAX request using the fancy fetch() API, Laravel would respond with 404 without any particular reason. I did not query an API route, neither did I use the api middleware group. I just wanted to use the same session-based authentication that I already had in place.

Solution

Turns out, the fetch() API does not attach cookies to the request by default. Laravel was receiving a request which could not be identified (no cookies = no session identifier), therefore was not able to recognise the logged in user. In order to send the cookies along with the request, you need to set credentials: 'same-origin' in the fetch’s configuration object. The call looks like this:

fetch(url, {
    credentials: 'same-origin',
})

Now, the request will contain the necessary cookies and the Laravel authentication system will be able to identify the user. 🎉

(Oh My) ZSH Symfony Completion

Jerguš Lejko — Tue, 03 Oct 2017 23:00:00 +0000

I am presenting you with my own Oh My Zsh plugin that brings command line autocompletion to your favorite tools such as laravel/artisan, laravel/valet, composer or ANY other command line tool built on symfony/console!

Follow the instructions on Github and bring life to your command line!

Backstory: How & Why

I am a huge fan of Oh My Zsh and a huge fan of Laravel. When I switched to Oh My Zsh, I have immediately fallen in love with “autocompletion plugins” for various tools such as git or brew. However, I was missing this functionality in tools I was using on daily basis: artisan and composer.

I have googled for suitable plugins but I was not totally satisfied with the ones I found. They were either outdated (new commands missing) or offered only fixed set of commands (it wouldn’t pick up your custom artisan commands). I decided to take a look at how are these plugins structured and come up with a new one that would cover all my needs.

My first goal was to create an “Artisan completion plugin” that would parse the output of php artisan and provide me with fully functional autocompletion. I managed to get the prototype working in a few hours and I was pretty happy with the result. Then is struck me! Laravel’s artisan is built on top of the symfony/console package. And so is composer!

I decided to generalize this plugin to support ANY tool built on symfony/console. That includes laravel/installer or even laravel/valet! To activate the autocompletion for your favorite tools, just specify the name of the tool in .zshrc. Take a look at the Github repository for further instructions.

So, here we are. Go ahead, try it and let me know what you think. Thanks.

DEV Community: Jerguš Lejko

Fetching Laravel

Issue

Solution

(Oh My) ZSH Symfony Completion

Backstory: How & Why