WebApi
WebApi copied to clipboard
PR for 7.6 Beta by making Patchhandler and related classes internal
Issues
This pull request fixes #xxx.
Description
PR for 7.6 Beta by making Patchhandler and related classes internal
Changes:
DeltaOfT internal void Patch(
DeltaSetOfT internal DeltaSet<TStructuralType> Patch(IC internal DeltaSet<TStructuralType> Patch(
EdmChangedObjectcollection internal EdmChangedObjectCollection Patch(OD
EdmODataAPIHandler internal abstract class EdmODataAPIHandler
IODataAPIHandler internal interface IODataAPIHandler
ODataAPIHandler internal abstract class ODataAPIHandler<TStructuralType>: IO
ODataAPIHandlerFactory internal abstract class ODataAPIHandlerFactory
ODataAPIResponseStatus internal enum ODataAPIResponseStatus
ODataEdmAPIHandlerFactory internal abstract class ODataEdmAPIHandlerFactory
ODataIDResolver internal abstract class ODataIDResolver
Checklist (Uncheck if it is not completed)
- [ ] Test cases added
- [ ] Build and test with one-click build and test script passed
Additional work necessary
If documentation update is needed, please add "Docs Needed" label to the issue and provide details about the required document change in the issue.
at least rebase and squash merge into one commit. and need other team member's review ahead.
Are these suppressions all still required?
Some seem to be repeats. Others may no longer be valid for the limited scope PR. Still others may be valid warnings that should be addressed, not supressed (like the unused private fields).
Try removing the suppressions and recompiling. For an issues raised, consider whether they should be fixed or suppressed.
Refers to: src/Microsoft.AspNet.OData/GlobalSuppressions.cs:148 in 9fd1ffa. [](commit_id = 9fd1ffa1bcc3d42ad3e9252c30e0182d58a7334e, deletion_comment = False)
private EdmDeltaType _edmType;
it appears that this is private field is no longer used, and can be removed?
In reply to: 992763166
Refers to: src/Microsoft.AspNet.OData.Shared/EdmDeltaDeletedEntityObject.cs:24 in 9fd1ffa. [](commit_id = 9fd1ffa1bcc3d42ad3e9252c30e0182d58a7334e, deletion_comment = False)
private EdmDeltaType _edmType;
it appears that this is private field is no longer used, and can be removed?
In reply to: 992763526
Refers to: src/Microsoft.AspNet.OData.Shared/EdmDeltaDeletedLink.cs:24 in 9fd1ffa. [](commit_id = 9fd1ffa1bcc3d42ad3e9252c30e0182d58a7334e, deletion_comment = False)
private EdmDeltaType _edmType;
it appears that this is private field is no longer used, and can be removed?
In reply to: 992763699
Refers to: src/Microsoft.AspNet.OData.Shared/EdmDeltaEntityObject.cs:21 in 9fd1ffa. [](commit_id = 9fd1ffa1bcc3d42ad3e9252c30e0182d58a7334e, deletion_comment = False)
private EdmDeltaType _edmType;
it appears that this is private field is no longer used, and can be removed?
Refers to: src/Microsoft.AspNet.OData.Shared/EdmDeltaLink.cs:24 in 9fd1ffa. [](commit_id = 9fd1ffa1bcc3d42ad3e9252c30e0182d58a7334e, deletion_comment = False)
This PR has 5787
quantified lines of changes. In general, a change size of upto 200
lines is ideal for the best PR experience!
Quantification details
Label : Extra Large
Size : +5285 -502
Percentile : 100%
Total files changed: 111
Change summary by file extension:
.csproj : +114 -43
.config : +103 -100
.cs : +4735 -333
.resx : +18 -0
.projitems : +25 -0
.bsl : +285 -24
.proj : +3 -0
.targets : +2 -2
Change counts above are quantified counts, based on the PullRequestQuantifier customizations.
Why proper sizing of changes matters
Optimal pull request sizes drive a better predictable PR flow as they strike a balance between between PR complexity and PR review overhead. PRs within the optimal size (typical small, or medium sized PRs) mean:
- Fast and predictable releases to production:
- Optimal size changes are more likely to be reviewed faster with fewer iterations.
- Similarity in low PR complexity drives similar review times.
- Review quality is likely higher as complexity is lower:
- Bugs are more likely to be detected.
- Code inconsistencies are more likely to be detetcted.
- Knowledge sharing is improved within the participants:
- Small portions can be assimilated better.
- Better engineering practices are exercised:
- Solving big problems by dividing them in well contained, smaller problems.
- Exercising separation of concerns within the code changes.
What can I do to optimize my changes
- Use the PullRequestQuantifier to quantify your PR accurately
- Create a context profile for your repo using the context generator
- Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the
Excluded
section from yourprquantifier.yaml
context profile. - Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your
prquantifier.yaml
context profile. - Only use the labels that matter to you, see context specification to customize your
prquantifier.yaml
context profile.
- Change your engineering behaviors
- For PRs that fall outside of the desired spectrum, review the details and check if:
- Your PR could be split in smaller, self-contained PRs instead
- Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).
- For PRs that fall outside of the desired spectrum, review the details and check if:
How to interpret the change counts in git diff output
- One line was added:
+1 -0
- One line was deleted:
+0 -1
- One line was modified:
+1 -1
(git diff doesn't know about modified, it will interpret that line like one addition plus one deletion) - Change percentiles: Change characteristics (addition, deletion, modification) of this PR in relation to all other PRs within the repository.
Was this comment helpful? :thumbsup: :ok_hand: :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.