added 2 n=bew evebt types: FriendRequestOperation,DeleteFriendRequest and their respective event handlers
added more JAVADOC for the newly created event handlers
fixed a logic issue, wehre the getFriendRequestEQSenderID function returned a data payload for the friendrequests, when exception was raised (e.g the reason for the exception is because the PostgreSQL query didn't return any values, that's the intended behavior)
added on the default switch statement on the filterGetRecord to throw an exception, instead of returning a false output (e.g soft error)
hidden the output of the user object @toString for security purposes
fixed a argument assignment misplacement on a friendRequest object, where on the getFriendRequest() query it mapped the recipient and sender's PostgreSQL output to the wrong order of the model class
Checklist
[ ] 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 manual/automated tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
Description
FriendRequestOperation,DeleteFriendRequest
and their respective event handlersgetFriendRequestEQSenderID
function returned a data payload for the friendrequests, when exception was raised (e.g the reason for the exception is because the PostgreSQL query didn't return any values, that's the intended behavior)filterGetRecord
to throw an exception, instead of returning a false output (e.g soft error)@toString
for security purposesgetFriendRequest()
query it mapped the recipient and sender's PostgreSQL output to the wrong order of the model classChecklist
Remark
For automation please see closing-issues-using-keywords