Introduce UTILMDG and UTILMDS for FV2310 #637
Annotations
10 warnings
|
EDILibrary/EdiJsonMapper.cs#L128
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
EDILibrary/EdiJsonMapper.cs#L151
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
EDILibrary/EdiJsonMapper.cs#L132
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
EDILibrary/EdiJsonMapper.cs#L359
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
EDILibrary/EdiJsonMapper.cs#L381
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
EDILibrary/EdiJsonMapper.cs#L381
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
EDILibrary/EdiJsonMapper.cs#L44
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
EDILibrary/EDIHelper.cs#L251
'EDIHelper.RemoveBOM(string)' is obsolete: 'Use 'RemoveByteOrderMark' instead'
|
|
EDILibrary/EDIHelper.cs#L289
'EDIHelper.RemoveBOM(string)' is obsolete: 'Use 'RemoveByteOrderMark' instead'
|
|
EDILibrary/EdiJsonMapper.cs#L392
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
The logs for this run have expired and are no longer available.
Loading