Problem
Right now any user with a valid auth token can retrieve any tag resource as long as they know the ID of the resource. We should return a 404 (Not found) error if someone tries to retrieve/update/delete a resource that does not have a matching account_id

Solution
In the show, update, and delete methods of the tag controller, let's add an authorize plug (middleware)

The following guides may be improved with unit test examples:

• https://github.com/danschultzer/pow/blob/master/guides/custom_controllers.md
• https://github.com/danschultzer/pow/blob/master/guides/sync_user.md
• https://github.com/danschultzer/pow/blob/master/guides/lock_users.md
• https://github.com/danschultzer/pow/blob/master/guides/user_roles.md

There's alread

We want to add Elixir.Faker.Pokemon.Ru.location/0.

If this is the first time you contributing check out this guide.

Comment below if you want to start working on the issue and never be afraid to ask questions.

If you contribute module that does not exist yet [here is a good example PR](elixirs/faker#288

With the recent release of Phoenix 1.5 🎉 https://elixirforum.com/t/phoenix-v1-5-0-released/30693
Now is a great time to go through this example/tutorial with a fresh pair of eyes and completely update it (including) links to code snapshots. We can also extend it to include auth_plug #25 🔐 and presence #32 🚀.

• Checkout master
• Create new branch e.g: `update-t

The package creation/splitting is heavily dependant on zones. Prevent deletion of the last available zone.