🎉🎉🎉 3.0 🎉🎉🎉

3.0 marks the start of stable development.
From now on, no more big overhaul changes. This package is ready to be used in production environments!

MAJOR developer experience changes, like a static API and easy-to-use setup. The experience was modeled after the already well-known exception flow to make it easier to pick up and use.

Also, SnapExit now enjoys a whole test suite to make sure it is reliable and compatible with any environment you throw at it. And Benchmark.NET was used to accurately show the performance benefit for multiple scenarios.

Go and have a look!

What's Changed

• 3.0 static service test by @ThatGhost in #5
• 3.0 - Snap exit made even better by @ThatGhost in #4

Full Changelog: Minor-release...3.0-Stable

V2.2

Version 2.2 brings more juicyness to SnapExit in the form of developer experience. The procces is streamlined and easy to work with.

It also added more tests, bug fixes and documentation updates.

Go check it out now!

What's Changed

• 2.2 implement feedback by @ThatGhost in #3

Full Changelog: Major-Release...Minor-release

V2.0

SnapExit V2.0!!

This release aims to address a large concern for many users.
Security and usability.

Previously i had a Middleware that would leverage SnapExit to return responses for ASP.NET Core api's. But this was obviously a bad practice since i could inject myself into the middle of api requests. I fixed this by creating a baseclass that allows users to define their own middleware.

But this also had the added benefit that you can now leverage SnapExit on any class, anywhere. So if you have a task anywhere in your flow you can use SnapExit's performance to achieve good exception-like behaviour throughout your code!

What's Changed

• it now works for anything and everything not just ASP.Core API by @ThatGhost in #1

New Contributors

• @ThatGhost made their first contribution in #1

Full Changelog: https://github.com/ThatGhost/SnapExit/commits/Major-Release