Added #14665: add checkout functionality to accessories

[arne-kroeger]

Added #14979: add checkout functionality to accessories

Description

Add feature to checkout accessories to locations or assets.

Added #14665
Added #12381
Added #12452
Added #11820
Added #10956
Added #5140 (parts of it)
Added #14979 (parts of it)

Type of change

Please delete options that are not relevant.

• New feature (non-breaking change which adds functionality)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Tests\Feature\Checkouts\Ui\AccessoryCheckoutTest::testAccessoryCanBeCheckedOutToLocationWithQuantity
• Tests\Feature\Checkouts\Ui\AccessoryCheckoutTest::testAccessoryCanBeCheckedOutToAssetWithQuantity

Test Configuration:

• PHP version: 8.3.9
• MariaDB version - 10.11
• Webserver version - php server
• OS version - Mac OS

Checklist:

• I have read the Contributing documentation available here: https://snipe-it.readme.io/docs/contributing-overview
• I have formatted this PR according to the project guidelines: https://snipe-it.readme.io/docs/contributing-overview#pull-request-guidelines
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[welcome]

💖 Thanks for this pull request! 💖

We use semantic commit messages to streamline the release process and easily generate changelogs between versions. Before your pull request can be merged, you should update your pull request title to start with a semantic prefix if it doesn't have one already.

Examples of commit messages with semantic prefixes:

• Fixed #<issue number>: don't overwrite prevent_default if default wasn't prevented
• Added #<issue number>: add checkout functionality to assets
• Improved Asset Checkout: use new notification method for checkout

Things that will help get your PR across the finish line:

• Document any user-facing changes you've made.
• Include tests when adding/changing behavior.
• Include screenshots and animated GIFs whenever possible.

We get a lot of pull requests on this repo, so please be patient and we will get back to you as soon as we can.

[snipe]

I don't understand what this is supposed to do, and there are definitely some breaking changes here. Not to mention that PRs should be put against the develop branch, not master, per the dev documentation.

[what-the-diff]

PR Summary

• Renaming of Variables and Relationships
  All instances of users in the code base, both as variables and relationships, were replaced with checkouts. This happens across multiple files, including app/Console/Commands/RestoreFromBackup.php, app/Helpers/Helper.php, app/Http/Controllers/Accessories/AccessoriesController.php, etc. The change ensures greater clarity and precision in variable naming, aligning with the actual function and purpose.

• Introduction of AccessoryCheckout Model
  A new model class AccessoryCheckout has been created, setting up one-to-one relationships with both Accessory and User models and introducing new methods for better asset assignment and search functionality.

• Update of User Model and AccessoryPresenter
  The User model and AccessoryPresenter class got a facelift as well, their respective methods changing from employing the users relationship to the checkouts relationship, maintaining consistency throughout the code base.

• Changes in AccessoryFactory Class
  The AccessoryFactory class was updated where it was creating a new AccessoryCheckout entry instead of attaching an accessory to a user, both in withoutItemsRemaining and checkedOutToUser methods.

• Migration to 'accessories_checkout' Table
  There was a migration from the accessories_users table to the accessories_checkout table, which also meant the addition of a new column called assigned_type.

• Changes in View Files
  The checkout.blade.php and view.blade.php view files were updated with edits made in table ID, column fields, and form fields to reflect the new changes better.

• Updated Testing Classes
  Two Test classes, AccessoryCheckinTest and AccessoryCheckoutTest, had their methods updated to use new field names and relationships, ensuring correct and efficient implementation and measurement of the intended changes.

Overall, these adjustments in variable terms, relationships, new methods, and structural changes in tables will make the code clearer and efficiently precise, leading to better overall performance.