Open goblinfactory opened 4 years ago
@hagbarddenstore did all of the work on this example project. The purpose was two-fold. One - an example to work on in parallel with library to get the user perspective, but then of course to serve as a general working example without anything specific in mind.
It surely needs some love, feel free to do what you see fit! I really like the idea of integrating some advice/documentation into the views.
Also, related to #79 which suggests adding an ISerializer based on System.Json to the core library and making it the default.
Ah, great. Happy to upgrade this to 3.1 LTS. and put in some docs. quick question, can you confirm this line is ok?
services.AddSingleton(services.AddSingleton(new EngineBuilder().Build<TodoModel>().GetAwaiter().GetResult()));
then I can start looking at a very simple update to the project.
Looks legit besides the duplicated services.AddSingleton!
haha...typo from copy and paste, doh! :D
I threw the todo example away and created a Trello clone instead using .NET Core 3.1
a709ea5f350885955ad8e878f9dc1c11742f6e36
I will be looking at this on Thursday. I have take Thursday and Friday off to do some open source coding.
Hi @rofr what's the status of the TODO MVC Sample app?
does that need to be upgraded to .net core 3.1? What's it's purpose? I couldnt get it to run without making a few small tweaks
As the code currently stands, when you run,
Kestrel
starts, but the memstate builder never builds the singleton instance. If you navigate tohttp://localhost:12202/lists
you get the following errorto fix this I had to change the
ConfigureServices
as follows, fromchange to
Also, if you're not running
postgres
you get an error initialising the serializer, so it's best to addMemstate.JsonNet
packageso that the only
sample project
that users see when they clone the project and press F5 will at least start and run. It's not an unreasonable expectation, which brings me back to wanting to know the purpose of the sample project? If we can define the purpose then I can make some changes to help deliver on that goal.Some idea:
Memstate
configuration andNpgsql
journal provider forpostgres
, if you want to try that out. The default (without this setting) will beMemstate.JsonNet
, which will create a journal file ...etc etc..pester
as part of the build, rather than complicating the unit tests? imho. I can help with that.