Fix enable liquidity button when sometimes the liquidity rules wont appear #201
Jossec101Annotations
11 warnings
|
build-and-test
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-dotnet@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
build-and-test:
src/Shared/UTXOSelectorModal.razor#L104
Found markup element with unexpected name 'Feedback'. If this is intended to be a component, add a @using directive for its namespace.
|
|
build-and-test:
src/Shared/UTXOSelectorModal.razor#L107
Found markup element with unexpected name 'Feedback'. If this is intended to be a component, add a @using directive for its namespace.
|
|
build-and-test:
src/Data/Models/WalletWithdrawalRequest.cs#L187
Nullability of reference types in type of parameter 'value' of 'void WalletWithdrawalRequest.Wallet.set' doesn't match implicitly implemented member 'void IBitcoinRequest.Wallet.set' (possibly because of nullability attributes).
|
|
build-and-test:
src/Helpers/Constants.cs#L117
Possible null reference assignment.
|
|
build-and-test:
src/Helpers/Constants.cs#L144
Possible null reference assignment.
|
|
build-and-test:
src/Helpers/Constants.cs#L191
Possible null reference assignment.
|
|
build-and-test:
src/Helpers/Constants.cs#L100
Non-nullable field 'NBXPLORER_URI' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
|
|
build-and-test:
src/Helpers/Constants.cs#L100
Non-nullable field 'PUSH_NOTIFICATIONS_ONESIGNAL_APP_ID' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
|
|
build-and-test:
src/Helpers/Constants.cs#L100
Non-nullable field 'BITCOIN_NETWORK' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
|
|
build-and-test:
src/Areas/Identity/Pages/Account/SetupSuperadmin.cshtml.cs#L78
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.
|