Commit Graph

10 Commits

Author SHA1 Message Date
54efb095fe style: run php-cs-fixer 2021-05-20 20:37:35 -03:00
e22f49bc6a Avoiding issues and refactoring code
I made the code more passive, avoiding issued at taking, returning,
storing alerts or removing alerts from an item.

Now they all check if it is with you before returning/deleting
alert etc. I am not sure if all cases are covered, but they are
better than before. I had one only issued on this on that time,
but I prefer to prioritize safety/security.

I took the opportunitie to move some code from Controllers to
the model itself, as they were changing with the DB.
2018-10-21 13:09:06 -03:00
1e1c178214 Refactoring: TakeController returned item Mail moved to a listener
The TakeController was manually sending the email message
as well as dealing with item return, so I moved the email message
to it's own listener, I created an event for it and moved the
return part to the item model.
2018-09-30 21:37:44 -03:00
4ef87f411d Including authenticaed user on models: Items, Product and User 2018-09-19 15:00:49 -03:00
c38744e392 Added Delete PRODUCT with Items and dettaching from users 2018-09-17 00:51:41 -03:00
ea3ffaad39 Including occupied username and renaming DB field
Now it shows the username of who is using an item.
Item db field 'usedBy' was renamed to 'used_by' to keep consistence.
2018-09-14 12:52:07 -03:00
fd9e145443 Creating relationships between users/items/products 2018-09-12 02:31:03 -03:00
7701c1a11d Imrpoving Item, Product and Users 2018-09-11 20:48:09 -03:00
bfdfa50af1 Including Items and Products views and controllers 2018-09-10 01:23:51 -03:00
fd3e4a67cf Including Item and Product migration, controllers and models 2018-09-09 00:26:57 -03:00