TabNavigation | Quick start | RecyclerView library

you can use option paramter

reference document.

The AvalonDock implementation is pretty weird. I remember having some troubles too when I had to use this control in a project. I think I know this control quite well. It is very badly implemented, in my opinion. Because they, for some reason, decided to implement this control itself using MVVM instead of making it simply MVVM ready. This makes it very inconvenient to use in advanced scenarios.
Semantics are also quite confusing. For example, containers are not the controls that render data. Containers are assigned to the Model property of the controls. Data is not assigned to the DataContext. But it looks good.

Also, the tab header placement behavior is broken (only allows tab headers at the bottom). My fix could be of interest for you, especially in context of dynamic tab header placement. See the Style below to get the expected tab header placement behavior. It simply wraps the content of the LayoutAnchorablePaneControl into a DockingPanel and rotates the header host, so that you get tab header alignment you have in Visual Studio (stacked by width). That's all. If you wish to stack the headers by their height (no rotation) simply replace the AnchorablePaneTabPanel with a e.g., StackPanel and remove the rotation triggers.
The provided example is based on that Style below. Otherwise you won't be able to propagate tab header position to the view.

Another big pain is the lack of events that are exposed by the DockingManager class and AvalonDock in general. This means there is no chance to observe the drag and drop actions. As a matter of fact, DockingManager only exposes three quite uninteresting events. Same to the content hosts like the LayoutAnchorablePaneControl.
Since AvalonDock does not use the WPF framework's Drag & Drop API, handling those events is not a solution.

To overcome the short comings, you must handle one of the few model events, the LayoutRoot.Updated event in this case.

The solution only targets the LayoutAnchorablePane and LayoutAnchorableGroupPane. To address advanced grouping or the LayoutDocumentPane you can simple extend the example by following the pattern.
Since you only require/requested a two column layout, the algorithm will do the job. Other more advanced layout arrangements are supported, but the behavior is not perfect as not all conditions are currently tracked. The focus is on a two column layout. It's a quick (but not so dirty) and very simple solution.
You should consider to disallow any layout arrangement other than the two column layout explicitly.

Additionally, AvalonDock does not provide an event to indicate when the visual layout process is completed. You only get a notification via the LayoutRoot.Updated event when the layout model is added/removed to/from the layout model tree. But you never know when exactly the visual tree is updated. We need to have access to the visual containers in order to set the LayoutPanelControl.TabStripPlacement property based on the new position of this control.
To overcome this, I used the Dispatcher to defer the access to the then initialized and rendered LayoutAnchorablePaneControl. Otherwise the tab header arrangement would be premature, because the control's layout index is yet to change. AvalonDock only allows to track very few layout model modifications but no observation of actual docking operations at all.

So the algorithm is basically

1. Handle the LayoutRoot.Updated event and start the actual positioning algorithm deferred using the Dispatcher
2. Iterate over all pane controls to update the tab header placement. In case nesting is allowed, you will have a layout tree that you have to traverse recursively, like it is done in this example for group panes.
3. Identify the position of the pane in the layout based on their index.
4. Set the LayoutPanelControl.TabStripPlacement property according to the index: an index of 0 means left and an index that equals the item count means right. Every other index is in between. The tab headers are placed based on the pane's position in the layout.
5. The DockingPanel will layout the tab items accordingly. Triggers are used to rotate the tab headers if they are positioned left or right.

There can be multiple LayoutPanelControl elements in the layout (except you disallow "illegal" layout arrangements to enforce the two column layout).

MainWindow.xaml.cs

The issue is the line const { input } = route.params; - before react-navigation populates the route object, you will get an error trying to reference its nested properties. Safely accessing the route object will prevent this, i.e.

const { input } = route?.params || {};

I have ToggleIcon inside the DataTemplete , that toggleIcon must be visible only for the selectedItem.How to do that?

You could define bool Visible property for the Model class to handle ToggleIcon visible.

For example

making the XAML list view header sticky with full scroll bar

The problem is you have placed the header out of the ScrollViewer, it could make the header sticky but the scroll bar will not full.

You have many ways to make sticky header, derive from your screenshot. it looks contain only one group. please check Windows Community Toolkit ScrollHeader, and use StickyHeaderBehavior directly.

For example

So I need to figure out a way to either pass in BasketItem, or BasketItemNutri, from the MainPage into custom user control.

You has placed NutriDetailsControl in the DataTemplate, so you can't use x:Bind to bind property in the code behind directly. For this scenario, the better way is that use bind element name then find it's DataContext

The MenuItem has different templates depending on the value of its Role property. Here is an example that you should be able to modify according to your requirements:

You can use a Trigger to set the IsSelected state depending on IsKeyboardFocusWithin in your item container style. Whenever you focus a TextBox, it will focus the row, too.

There is an approach could be used to access the BlueLine object in code behind when a ListViewItem is selected by using VisualTreeHelper class.

Please check the following code:

Add headers and namespaces: