Closed frg2089 closed 4 months ago
Nightly build for this pull request:
Should I fixed #515 in this PR?
Should I fixed #515 in this PR?
I think not unless your want your PR being reviewed for months
Warning NU1903 seems to be critical one.
Warning NU1903 seems to be critical one.
We cannot fix it now. Because the ImageSharp 3 are not supported .Net Framework. We must have another solution to replace ImageSharp. such as SkiaSharp. It should be resolved in another PR.
[!note] SkiaSharp only supported
.jpg
,.png
and.webp
formats.
Warning NU1903 seems to be critical one.
Just ignore it. The client only loads pictures from local files instead of Internet so it is pretty fine to ignore this high risk.
Obsolete. See messages below
Warning NU1903 seems to be critical one.
We cannot fix it now. Because the ImageSharp 3 are not supported .Net Framework. We must have another solution to replace ImageSharp. such as SkiaSharp. It should be resolved in another PR.
Note
SkiaSharp only supported
.jpg
,.png
and.webp
formats.
https://github.com/SixLabors/ImageSharp/releases/v2.1.7
They released v2.1.7 to backport for .NET Framework an hour ago. Upgrading to this version should be fine
Warning NU1903 seems to be critical one.
Just ignore it. The client only loads pictures from local files instead of Internet so it is pretty fine to ignore this high risk.
The upcoming MapDB 2.0 may change that status quo, so I am not sure if it's fine. We must also account possible future features too.
Warning NU1903 seems to be critical one.
Just ignore it. The client only loads pictures from local files instead of Internet so it is pretty fine to ignore this high risk.
The upcoming MapDB 2.0 may change that status quo, so I am not sure if it's fine. We must also account possible future features too.
That message is obsolete since v2.1.7 is released
The upcoming MapDB 2.0 may change that status quo, so I am not sure if it's fine. We must also account possible future features too.
That message is obsolete since v2.1.7 is released
That's fine, I just wanted to highlight the importance of foreseeing the future changes in general.
Let's merge this after the ImageSharp upgrade that fixes the issue.
Close #512 48046a6b0794a337829ccba25093eb256708431c Close #501 4e8a9a18c80aa55d2e3ab02389ae04fd29297a1b