MicrosoftDocs
Split requirements for inlining to make more understandable
The current list of requirements is a mixture of requirements for the function definition and requirements for the context it is being used in. There are also duplicate requirements in the examples section.
This change splits the list into requirements for the function AND another list for the requirements of the context. It also removes the duplicate "examples" and refers users to the concise list.
@simonsabin : Thanks for your contribution! The author(s) have been notified to review your proposed change.
![prmerger-automator[bot] avatar](https://avatars.githubusercontent.com/u/22479449?v=4 "Published by a pub.dev verified publisher"){kind=small}
Learn Build status updates of commit 769ed9f:
:white_check_mark: Validation status: passed
| File | Status | Preview URL | Details |
|---|---|---|---|
| docs/relational-databases/user-defined-functions/scalar-udf-inlining.md | :white_check_mark:Succeeded |
For more details, please refer to the build report.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
![learn-build-service-prod[bot] avatar](https://avatars.githubusercontent.com/in/237442?v=4 "Published by a pub.dev verified publisher"){kind=small}
@s-r-k
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-team
@simonsabin Thanks, we're doing a separate internal PR to incorporate your changes, and you'll still get credit. When that PR merges, this one will automatically close.
