Skip to content

nullables wtf

nullables wtf #61

Triggered via push November 14, 2023 05:42
Status Success
Total duration 1m 30s
Artifacts

main.yml

on: push
Publish to GitHub
45s
Publish to GitHub
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
Build
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.
Build: src/Book.cs#L7
Non-nullable property 'Items' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build: src/Handlers/CacheHandler.cs#L33
Possible null reference return.
Build: src/Models/Manga.cs#L18
Non-nullable property 'Name' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build: src/Models/Manga.cs#L23
Non-nullable property 'Url' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build: src/Models/Manga.cs#L28
Non-nullable property 'Cover' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build: src/Models/Manga.cs#L33
Non-nullable property 'Summary' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build: src/Models/Manga.cs#L38
Non-nullable property 'Author' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build: src/Models/Manga.cs#L43
Non-nullable property 'SourceId' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build: src/Models/Manga.cs#L58
Non-nullable property 'Metonyms' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.