Skip to content

Latest commit

 

History

History
29 lines (19 loc) · 1.34 KB

0008_navigation-based-on-search.md

File metadata and controls

29 lines (19 loc) · 1.34 KB

Notes

  • I want something similar to stack overflow where the navigation is based on the search bar.

  • I could add a navigation service that looks like this:

    void NavigateToSearch(SearchQueryData searchQueryData);
void NavigateToPageDetails(long pageId);
void NavigateToTagTree(IList<string> requiredTags);
void NavigateBack();

    However, I feel that this API would be very inconsistent.

  • We could handle this in the view model, but I can't get access to the NavigationService from the Frame in any reliable way.

    • I tried using a DependencyProperty, but the constructor will run before that will be set to anything.

  • Essentially, I need a state machine that can be in three states: Search{ SearchQueryData }, Page{ PageId } or Tags{ RequiredTags }. One method would be to add more stuff to SearchQueryData or to add a wrapper type that can contain any of them.

  • Currently, my approach is to have a RoutingService that has Navigate(RouteData) functions. This will emit an event if the route changes and the <MainWindow> will change what it contains based on this.

    • I don't like this approach, it makes the code very difficult to comprehend.

    • Currently, the search is broken because a new PageListViewModel is created every time. This will automatically set a new search query if I remember correctly.