Skip to content

Refactor ViewModels and Views for naming consistency #919

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

Merged
merged 2 commits into from
Nov 5, 2024

Conversation

vb2ae
Copy link
Member

@vb2ae vb2ae commented Nov 4, 2024

Renamed parameters in ActionsViewModel.cs methods for clarity.
Removed unused usings and updated VisualStateResult in CoroutineViewModel.cs.
Renamed private fields and properties in NavigationSourceViewModel.cs.
Updated property names in NavigationTargetViewModel.cs.
Renamed controls and updated bindings in ActionsView.xaml.
Changed VisualState name in CoroutineView.xaml.
Renamed controls in NavigationSourceView.xaml and NavigationTargetView.xaml.

Closes #913

Renamed parameters in ActionsViewModel.cs methods for clarity.
Removed unused usings and updated VisualStateResult in CoroutineViewModel.cs.
Renamed private fields and properties in NavigationSourceViewModel.cs.
Updated property names in NavigationTargetViewModel.cs.
Renamed controls and updated bindings in ActionsView.xaml.
Changed VisualState name in CoroutineView.xaml.
Renamed controls in NavigationSourceView.xaml and NavigationTargetView.xaml.
@vb2ae vb2ae linked an issue Nov 4, 2024 that may be closed by this pull request
Updated some property names in the xaml
@KasperSK KasperSK merged commit 496d021 into master Nov 5, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Fix warnings in Features apps
2 participants