katie kaitlynbrown

## keybase.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                kaitlynbrown
                / keybase.md
            
            
              Created
              September 11, 2019 14:09
            
          
    Keybase proof

I hereby claim:

I am kaitlynbrown on github.
I am allophyl (https://keybase.io/allophyl) on keybase.
I have a public key ASBY27xBCTOBnBWO5XZRoNqFGnlS2zS3ueoqxMZ3CNtJswo

To claim this, I am signing this object:

  
## _original_post_with_code_formatting_error.txt
On a page where I am displaying a receipt to a user, I have a section which lists the subtotal, any taxes, and the total. Since the taxes applicable vary by region and based on the products being sold, the number of rows in this section will vary. For example, here are 3 separate orders, one with GST and PST, one with just GST, and one with neither:

[![GST+PST][1]][1]
[![GST Only][2]][2]
[![No Tax][3]][3]

I've accomplished this by putting just the SubTotal in the grid in XAML, and adding the rest in the code-behind in a method I call from the ViewModel. However, I'd really like to avoid doing it this way, so I'm wondering if there is an approach to accomplishing this which doesn't require having a bunch of code in the View's code-behind and having the ViewModel know about the View.

A ListView is not suitable here for a number of reasons:
	On a page where I am displaying a receipt to a user, I have a section which lists the subtotal, any taxes, and the total. Since the taxes applicable vary by region and based on the products being sold, the number of rows in this section will vary. For example, here are 3 separate orders, one with GST and PST, one with just GST, and one with neither:

	[![GST+PST][1]][1]
	[![GST Only][2]][2]
	[![No Tax][3]][3]

	I've accomplished this by putting just the SubTotal in the grid in XAML, and adding the rest in the code-behind in a method I call from the ViewModel. However, I'd really like to avoid doing it this way, so I'm wondering if there is an approach to accomplishing this which doesn't require having a bunch of code in the View's code-behind and having the ViewModel know about the View.

	A ListView is not suitable here for a number of reasons: