Update version to 2.0.1 with new changes #71
Annotations
10 warnings
|
deploy-to-ghp-branch:
Components/InsertUrlDialog.razor#L23
Non-nullable property 'MudDialogInstance' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
deploy-to-ghp-branch:
Components/SettingsDialog.razor#L23
Non-nullable field '_colorValue' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
|
|
deploy-to-ghp-branch:
Components/SettingsDialog.razor#L21
Non-nullable property 'MudDialogInstance' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
deploy-to-ghp-branch:
Components/UpdatesEntry.razor#L53
Non-nullable property 'Changes' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
deploy-to-ghp-branch:
Components/UpdatesEntry.razor#L52
Non-nullable property 'New' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
deploy-to-ghp-branch:
Components/UpdatesEntry.razor#L51
Non-nullable property 'Title' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
deploy-to-ghp-branch:
Services/GlobalErrorService.cs#L7
Non-nullable field '_snackbar' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
|
|
deploy-to-ghp-branch:
Pages/Info.razor#L45
Non-nullable field 'timer' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
|
|
deploy-to-ghp-branch:
Pages/Info.razor#L49
Nullability of reference types in type of parameter '_' of 'void Info.Tick(object _)' doesn't match the target delegate 'TimerCallback' (possibly because of nullability attributes).
|
|
deploy-to-ghp-branch
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.
|