v0.3.0

Sessions Collision/GC fix !

One issue that Sharp had with the session system is that, when hosting two applications on the same host, sessions would collide, meaning that if you login/logout on application A, your session data would be set on application B too !
In an attempt to fix this, the session_path option was used to store the Session files in the application storage directory, it worked; But then, another issue came up, the fact that when using a custom session path, PHP's garbage collector would ignore it, and you'll have to delete the files by yourself.

Today, I've found this answer on StackOverflow, which seems to fix this issue. No need to clear session files anymore ! 🥳 🙏

Code Cleaning / Misc changes

(Some method were renamed, old versions are not deleted but marked as @deprecated)

• NEW Response::octetStream method
• NEW Model 'updateId' and 'deleteId' methods !
• Public readonly Authentication properties
• ObjectArray 'combine' renamed to 'toAssociative'
• Response 'render' method renamed to 'view'