Which delay for v1 #380
Replies: 3 comments 2 replies
-
The final word is up to @iammukeshm, but I would think that the api is starting to get into its final shape. I personally will start my project with it very soon... The blazor client OTOH needs some more serious polish though... but I don't think that stands in the way of starting an actual project... changes there will be easier to port over after starting a project I would think (no dependencies like EFCore Migrations or stuff like that). Actually, I've already started the project, and set it up with an "upstream" git remote back to my fork of the fullstackhero... quite easy to pull in changes that way! That will start to get tricky once I have an actual database running in production with migrations and stuff I think... but we'll cross that bridge when we get there ;-) |
Beta Was this translation helpful? Give feedback.
-
Thanks for your answer @fretje My dreaming goal to the end of 2022 years is APi Multitenant with this boilerplate and a Flutter client :-) |
Beta Was this translation helpful? Give feedback.
-
v1 will be out as soon as possible. As @fretje mentioned, we are almost there. I am working on the documentation. Few open issues are there on API and Blazor, though very minor. I have not been able to invest much time past 3 weeks because of another commitment, but yeah, we will make it soon ;) |
Beta Was this translation helpful? Give feedback.
-
Hi guys,
I saw the integration of ardalis.Specification and Finbuckle.MultiTenant that looks great improvement. (Thanks @fretje )
Do you know if a lot of changes are coming or you can estimate that the v1 is soon. @iammukeshm
I 'll start my project when the code will be more stable.
Thanks for your answer
Beta Was this translation helpful? Give feedback.
All reactions