For now we can discuss if there's a possibility to support this soon or in the Future
@sbwalker Sorry for the delay in responding. I'm thinking of building a large scale app, like a Student Information System - something that would run a university. I would build up the app by creating modules. First would be a Student module, then a Registered Courses module, but of course the Registered Courses module depends on having the Student module installed and running. I can see this type of dependency in a lot of design. Otherwise I would have to build the monolith module.
I have been working on a few larger scale enhancements recently, and will be submitting a large PR soon. Most successful application frameworks offer capabilities for sending notifications and I have added a service which allows the system to send notifications to users and for users to send notifications to each other. The service decouples the notifications from the actual delivery - so there is a repository for the notifications and a separate service which handles delivering them as emails asynchronously via SMTP. This notification system was critical for user interactions such as email verification during new account registration as well as password reset functionality - which have also now been implemented.
@mikecasas as Michael Washington mentioned, modules are loosely coupled by design. As a result dependencies between modules are not a component level concern but rather an integration/application concern. Applications are usually comprised of many modules and the dependencies between modules are managed via routing and permissions. Each module can be its own project/DLL from a deployment perspective which permits a low level of granularity. You can also package multiple DLLs into your Nuget package if you want to create a composite app package which installs all of your modules together.
That is a great question Mike. During 2019 there was a fairly long roadmap of features which was posted on the main project Github page. I removed each item from the list as it was completed. As you can see there are no items remaining for what I would consider "MVP". That being said, Michael Washington pointed out in late 2019 that in order to use Oqtane in production you would need some of the remaining user scenarios implemented such as email verification and password reset. This led to an increase in scope as I realized that a robust user notification system was needed in order to support it. This work was recently completed. At this point there is a lot of functionality in this framework and I think it needs some thorough testing to ensure it is 100% stable and works as expected. I expect this will reveal a laundry list of bugs where community involvement would be highly appreciated.
In regards to Localization I will refer to the project philosophy blog https://www.oqtane.org/Resources/Blog/PostId/538/oqtane-philosophy and the section about Microsoft Alignment. My preference is to wait for guidance from Microsoft on the recommended way to implement localization in Blazor, rather than trying to come up with our own solution.
Regarding Client-side mode there's some ways to make it happen
IMHO we shouldn't rely on resx files for many reasons
I prefer to create a custom JSON provider like what I did in one of my open source projects, because JSON is play nicely in both server and client
@hishamco Absolutely! Like I said in my earlier post, there was a roadmap posted on the main Github page in 2019 and I removed the items as they were implemented. Probably not the right approach. I should have left the full list on the page and simply indicated which items were done. I will add it back.
Also we need to know what's the features that we need to implement
I'm glad to contribute into Oqtane, especially localization stuff 😉
Would it be beneficial to start some type of documentation site/repo? I know there are some screenshots on the readme of the main repo. Maybe some thing like https://readthedocs.org/ Also where should
questions be asked? On the Gitter channel or in the Github issues? I like how a project has their Github new issue template, it specifically directs them where to go for certain items.
questions be asked? On the Gitter channel or in the Github issues? I like how a project has their Github new issue template, it specifically directs them where to go for certain items.
They are easily to edit, but I am not sure if there's possibility to contribute to edit them
as the host user
Is this happen after the latest commit?
Sorry I meant PR #210
yes, appsettings.json is supposed to be there. I merged PR #213 this morning from fileman and I could see that he mistakenly committed appsettings.json with a connection string and then subsequently removed it. However the merge actually removed the file from the repo.
I am not personally able to commit a new appsettings.json as I have my local git configured to ignore that file ( so that I do not commit it by mistake )
Can someone please submit an empty appsettings.json as a PR
@mikecasas after the recent authorization changes there is a lot of regression testing needed. It is possible that the add page was affected; however, I would re-install to be sure ( ie. remove the connection string in appsettings.json and run the app )