[Tech] [Ajay]: Add id to section #109
ajaysskumargenerate-gh-pages-output.yml
on: push
build-and-deploy
1m 23s
Annotations
10 warnings
|
build-and-deploy:
TestArena/Blog/Common/Header.razor#L7
Non-nullable property 'Authors' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
build-and-deploy:
TestArena/Blog/Common/Header.razor#L5
Non-nullable property 'Image' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
build-and-deploy:
TestArena/Blog/Common/Header.razor#L4
Non-nullable property 'Title' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
build-and-deploy:
TestArena/Blog/Common/List.razor#L4
Non-nullable property 'Heading' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
build-and-deploy:
TestArena/Blog/PactNet/Intro/Index.razor#L6
Possible null reference assignment.
|
|
build-and-deploy:
TestArena/Blog/Common/Section.razor#L4
Non-nullable property 'Heading' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
build-and-deploy:
TestArena/Blog/PactNet/pact-broker/Index.razor#L6
Possible null reference assignment.
|
|
build-and-deploy:
TestArena/Blog/Common/TextDecorators/FileRef.razor#L9
Non-nullable property 'FilePath' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
build-and-deploy:
TestArena/Blog/Common/TextDecorators/FileRef.razor#L6
Non-nullable property 'FileName' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
build-and-deploy
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
|