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'

v0.2.0: Queues & FTP (And some fixes)

New features

This release includes :

• new QueueHandler trait
• support for FTP Storage

With some little fixes/features too !

• DatabaseQuery now wrap insert field names inside backticks
• Request fetch() method now have a debug level parameter (described in Request documentation)
• Router don't cache routes with non-array callable middlewares
• Utils: better exploreDirectory() behavior fix, now directly ignore "." & ".." (instead of slicing scandir results)
• Renderer handle errors in a better way
• Route hex & uuid slug formats

Breaking changes

• CustomEvent is now in Sharp\Classes\Events (was in Sharp\Classes\Core)

NEW commands

• list-queues
• clear-queues
• clear-caches

v0.1.0

Hurrah ! 🎉

Sharp's first release is here

This release includes every base feature needed to make a Web site, they are all described in README.md and in the documentation

Important

As this version is still under v1.0, major changes can still happen to the API

What is coming next ? 🚀

• If everything goes fine, a website for the project should arrive not-too-long after this release
• More Utilities commands should be made to make app building even more easy
• Even if the code is tested in its actual state, more bugs are to discover and more fixes are to be made
• Making Sharp production-ready as fast as possible