Releases: polterguy/magic
Making sure Unit Tests pass
Oops, the unit tests didn't pass in the previous release. Note2Self: Setup TravisCI in Magic main project website ... (blush!)
Fixed log4net error
Unfortunately, the previous release missed a NuGet package reference in the magic.backend/magic.backend.csproj file - Sorry about that ...
Fixed!
Unit tests +++
This release contains unit tests for all submodules, in addition to "magic.common.tests" allowing you to easily unit test your own controllers, with helper classes and methods to use SQLite in-memory for your database ISession
nHibernate sessions.
In addition, ISession
is not being resolved according to a name, allowing us to use a different nHibernate session, depending upon whether or not you need to access an nHibernate session in a background worker thread or not. This fixes a severe bug with among other things the Magic Email project, which would try to persist emails to your database in a background thread on a closed nHibernate session (sorry about that).
In general, this is a very thorough and stable release compared to the previous releases, and only Magic Email and (Magic Cookie)[https://github.com/polterguy/magic.cookie] does not have almost 100% unit test coverage at the moment, which I'll fix later.
After you've downloaded Magic, feel free to check out any of these modules for it.
Especially Magic IO from above should be of interest to most of your projects, since it effectively wraps everything you need related to uploading and downloading files through your web API.
Maintenance release
Minor changes to folder structure
Maintenance release
Minor changes
Fixed error in template
The template for generating a new magic app using the botnet CLI contained a bug which prohibited it from functioning correctly with version 2.2.105 of the botnet CLI. This error should be fixed in this release.
Maintenance release
Minor maintenance release
dotnet CLI template + unit tests
Thanks to Jamie Taylor, we now have dotnet CLI template support, allowing you to install Magic as a CLI template, which again allows you to create a new Magic app by simply typing in something similar to the following.
dotnet new magic --name foo
The above will create a "foo" solution, with all "foo" projects and namespaces, with all the relevant projects automatically renamed. The scaffolding process also have additional settings, which you can see by issuing the following terminal command
dotnet new magic --help
In addition, Magic also now automatically creates unit tests for you, testing all controller endpoints automatically, as long as you implement the CrudTest<T>
class on your Xunit tests.
Super DRY Magic
v1.1 Oops ...