Progress

27.10.23

• tried to get an over view of the Laravel components: LaravelComponents.md
• completly new Laravel installation
• added mogration, model, controller and routes for Location, Member, Staff and Booking
• Staff and Member are using the same User table, but have different role
• relationships are setted up:
• • Location has many Staff
• • Location has many Member
• • Staff has many Member
• • Member has many Booking
• added factory and seeder for all models
• using Bruno for testing the API, all files are in the Bruno folder
• added login via API
• there are three Users to test the login:
  • [email protected]
  • [email protected]
  • [email protected] Password for all is password
• added CRUD for Staff -> Member
• binded name, emailand role from the User Modell to the Member Modell
• tried to write a jurnal for the progress: jurnal.md, but it is now partially outdated
• project ist ready to use, SQLite database and no secrets in the .env file
• initial commit

03.11.23

• rebuild the way to divide the User-roles (using Middleware)
• moved the code from the MemberController to the Member Model
• use Scopes to filter the Member
• use select & join to get the data from the database
• made a benchmark against withs and joinis faster
• added inviteMail endpoint to send an email to a new Member
• added register endpoint to register a new Member
• use the customJson to format the response inkl. Exception handling

Issues

1. handle two different roles (staff, member) with the same user table is annoying. For every request we need to check the role and get the data from the right table. And both table have timestamps. Is there a better way?
2. There will be no response after a Member is deleted
3. I a non existing Member is requested, there will be an ugly response:"message": "No query results for model [App\\Models\\Member]
4. decide if we sort out the active member in the backend (/member?active) or in the frontend

ToDo

• better error messages:
• • if a Member is deleted, there should be a response
• • if an email is already in use and a new Member is created with this email, there should be a response

Links:

• How to Send Email in Laravel 9 using SMTP | All PHP Tricks
• Building a Role-Based REST API with Laravel Sanctum
• Laravel Telescope - Laravel 10.x - The PHP Framework For Web Artisans
• Junior Code Review: Laravel Routes, Middleware, Validation and more - YouTube
• 7 "Tricks" With dd() in Laravel
• Adding some Laravel magic to your Eloquent joins
• Laravel Soft Deletes - Papierkorb-Funktion für Eloquent | a coding project
• Best way to flatten a json column on the model
• alexeymezenin/laravel-best-practices: Laravel best practices
• Global scope in Laravel, the easy way. - DEV Community
• Move Model Scopes To Traits In Laravel | by Code Axion The Security Breach | Medium
• sveltekit-starter/src/hooks/laravel-sanctum.ts at develop · daison12006013/sveltekit-starter
• dedoc/scramble: Modern Laravel OpenAPI (Swagger) documentation generator. No PHPDoc annotations required.
• Authentication in Svelte using cookies - LogRocket Blog
• A simple way to enable CORS on Laravel - DEV Community

  Not used, but maybe useful in the future

• Laravel Active Trait
• bryanmylee/svelte-headless-table: Unopinionated and extensible data tables for Svelte
• svelte-plugins/datepicker: A simple datepicker component designed for Svelte.
• Use events • REPL • Svelte
• Laravel Database Structure: 11 Mistakes Developers Make
• How to Set Up and Use Vue 3 in Your Laravel 10 App with Vite.

Eloquent question, get relationship from collection

php - Laravel get a collection of relationship items - Stack Overflow

Responses and Status Codes

All requests and responses are of an application/json content type and follow typical HTTP response status codes for success and failure.

• 200 - Everything is OK
• 201 - Created Successfully
• 202 - Accepted
• 204 - No Content
• 301 - Moved Permanently
• 400 - Bad Request
• 401 - Unauthorized
• 404 - Not Found
• 500 - Internal Server Error

The API follows the general rule that all 200 codes are deemed successful, 300 codes denote a redirection, 400 codes are client errors and 500 codes are server errors.

Actions Handled By Resource Controller