Uh oh!
There was an error while loading. Please reload this page.
Enable nullable annotations for M.E.L.Abstractions - #43892
Conversation
ghost
commented
Oct 27, 2020
Tagging subscribers to this area: @maryamariyan |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Note for reviewer: _values is not null due to what Count returns on line 76
Uh oh!
There was an error while loading. Please reload this page.
edae4e5 to
8df11e4CompareUh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
please make sure owner of this library double checks the annotations of the ref
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Did you intend to check in these changes?
There was a problem hiding this comment.
yes this was intentional otherwise wouldn't have been able to add NetCoreAppCurrent for the project I think.
cc: @safern
There was a problem hiding this comment.
The reason behind adding NetCoreAppCurrent for these projects was to have CI protection for the nullable annotations to actually be correct and not broken on by upcoming changes but to actually not ship that asset. However the only caveat that this brings is that by adding this I'm not sure if people can just clone the repo and build this project without pre building anything else which was an effort @ViktorHofer did in the past.
There was a problem hiding this comment.
yes this was intentional otherwise wouldn't have been able to add NetCoreAppCurrent for the project I think.
This property is for convenience only, in case you don't want to list all the individual assembly references. In this case I think it's fine as we don't ship the `$(NetCoreAppCurrent)' asset.
However the only caveat that this brings is that by adding this I'm not sure if people can just clone the repo and build this project without pre building anything
Unfortunately with our current infra that's true but I don't think we should see that as a blocker. I would like to improve our infra so that $(NetCoreAppCurrent) builds via dependencies without an up-front build which would also enable VS builds for .NETCoreApp without up-front steps.
Uh oh!
There was an error while loading. Please reload this page.
70e6b56 to
c3e738bCompareto allow annotations on relevant projects, not yet enabled
c3e738b to
0ad32e6Compare@stephentoub@krwq@tarekgh looked at all the comments and made all the changes I was planning to do. I posed this question in #43892 (comment) too.
let me know what you think. |
maryamariyan
commented
Nov 9, 2020
Updates on PR since it was last reviewed:
|
maryamariyan
commented
Nov 12, 2020
@stephentoub@krwq could you please re-review? |
ViktorHofer
commented
Nov 12, 2020
Uh oh!
There was an error while loading. Please reload this page.
…ons-null Conflicts: src/libraries/Microsoft.Extensions.Logging.Abstractions/src/Microsoft.Extensions.Logging.Abstractions.csproj
ghost
commented
Nov 17, 2020
Hello @maryamariyan! Because this pull request has the p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me ( |
stephentoub
commented
May 24, 2021
@maryamariyan, doesn't the ref csproj need |
cc: @buyaa-n@safern
Related to #43605