Improve bind:get/set coverage
          #36250
        
          
      
                
     Merged
            
            
          
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Fixes #36052
Distilled from Javier's remarks at dotnet/aspnetcore#57962 (comment).
Tom or Wade: Ready here! This is just mirroring some really nice remarks that Javier made in a PU discussion ☝️ that devs will likely find helpful in understanding why they shouldn't write directly to component parameters, favoring
@bind:get/setdirective attributes instead. This adds a little more juice to the existing section and example on binding across components. I only need one review to get this in.For reference, here's one of the examples (because you can't see them here with the cross-repo links) ...
https://github.com/dotnet/blazor-samples/blob/main/10.0/BlazorSample_BlazorWebApp/Components/NestedChild.razor
Internal previews