Skip to content

<inheritdoc/> should not be used on partial properties.#1176

Open
caverna wants to merge 2 commits intoCommunityToolkit:mainfrom
caverna:feature/dev
Open

<inheritdoc/> should not be used on partial properties.#1176
caverna wants to merge 2 commits intoCommunityToolkit:mainfrom
caverna:feature/dev

Conversation

@caverna
Copy link
Copy Markdown

@caverna caverna commented Apr 1, 2026

**Closes #1068 **

PR Checklist

  • Created a feature/dev branch in your fork (vs. submitting directly from a commit on main)
  • Based off latest main branch of toolkit
  • PR doesn't include merge commits (always rebase on top of our main, if needed)
  • Tested code with current supported SDKs
  • New component
    • Pull Request has been submitted to the documentation repository instructions. Link:
    • Added description of major feature to project description for NuGet package (4000 total character limit, so don't push entire description over that)
  • Tests for the changes have been added (for bug fixes / features) (if applicable)
  • Header has been added to all new source files (run build/UpdateHeaders.bat)
  • Contains NO breaking changes
  • Every new API (including internal ones) has full XML docs
  • Code follows all style conventions

Other information

I simply can't run the tests on my PC.
Tons of building errors, even with a fresh code download

@caverna
Copy link
Copy Markdown
Author

caverna commented Apr 1, 2026

@dotnet-policy-service agree

@caverna caverna changed the title Feature/dev <inheritdoc/> should not be used on partial properties. Apr 3, 2026
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.

<inheritdoc/> should not be used on partial properties.

1 participant