New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate Blazor components to ComponentBase style ViewModels #72
Comments
@csharpfritz I can have a crack at this if you like? |
Assigned to you @SimonGeering |
@csharpfritz As it stands the dev branch gives the following error if you pull a clean fork, run the restoreDb.cmd and register a user:
I could either: B) Wait for you to fix the above bug and/or improve the "I'm a new contributor experience" when first doing a GitClone of a fork - further to my points in #42 so the app runs and a test account can be logged into based on some instructions in readme.md Let me know which way you would like to proceed, please. |
Additionally in terms of solution structure and layout - would we want to remove the ViewModel folder and instead move to a more functional file structure by adding, for each razor file, a corresponding xxx.Component.cs file in the Pages folder? This would help group code by functional area in one place, similar to the Angular feature-based naming structure |
@SimonGeering try to do a ef migration. It should fix your error |
It looks like the fixes that were added on stream for the preview 8 update will un-block this. I will pick it up after that is PR to the main repo |
As agreed in #72 this PR will switch all view models to inherit ComponentBase
DayPickerViewModel is a good example of using this technique
The text was updated successfully, but these errors were encountered: