Skip to content

Merge pull request #64 from HeinHtetAung-Dev/main #103

Merge pull request #64 from HeinHtetAung-Dev/main

Merge pull request #64 from HeinHtetAung-Dev/main #103

Triggered via push August 18, 2024 09:01
Status Success
Total duration 3m 37s
Artifacts

ci.yaml

on: push
Matrix: Build and Test
Code Scanning
2m 1s
Code Scanning
Fit to window
Zoom out
Zoom in

Annotations

41 warnings
Build and Test (6.0.x, ubuntu-latest): REMS.Models/Transaction/TransactionResponseModel.cs#L13
Non-nullable property 'Transaction' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build and Test (6.0.x, ubuntu-latest): REMS.Models/Transaction/TransactionResponseModel.cs#L14
Non-nullable property 'Client' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build and Test (6.0.x, ubuntu-latest): REMS.Models/Transaction/TransactionResponseModel.cs#L15
Non-nullable property 'Property' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build and Test (6.0.x, ubuntu-latest): REMS.Models/Transaction/TransactionRequestModel.cs#L17
Non-nullable property 'Status' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build and Test (6.0.x, ubuntu-latest): REMS.Models/Appointment/AppointmentDetail.cs#L27
Non-nullable property 'appointmentDetails' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build and Test (6.0.x, ubuntu-latest): REMS.Models/Transaction/TransactionModel.cs#L17
Non-nullable property 'Status' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build and Test (6.0.x, ubuntu-latest): REMS.Models/Review/ReviewResponseModel.cs#L5
Non-nullable property 'Review' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build and Test (6.0.x, ubuntu-latest): REMS.Models/Review/ReviewListResponseModel.cs#L7
Non-nullable property 'DataList' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build and Test (6.0.x, ubuntu-latest): REMS.Models/Review/ReviewListResponseModel.cs#L9
Non-nullable property 'PageSetting' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build and Test (6.0.x, ubuntu-latest): REMS.Models/Client/ClientListResponseModel.cs#L13
Non-nullable property 'DataLst' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build and Test (8.0.x, ubuntu-latest): REMS.Models/Transaction/TransactionResponseModel.cs#L13
Non-nullable property 'Transaction' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Build and Test (8.0.x, ubuntu-latest): REMS.Models/Transaction/TransactionResponseModel.cs#L14
Non-nullable property 'Client' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Build and Test (8.0.x, ubuntu-latest): REMS.Models/Transaction/TransactionResponseModel.cs#L15
Non-nullable property 'Property' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Build and Test (8.0.x, ubuntu-latest): REMS.Models/Transaction/TransactionRequestModel.cs#L17
Non-nullable property 'Status' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Build and Test (8.0.x, ubuntu-latest): REMS.Models/Transaction/TransactionModel.cs#L17
Non-nullable property 'Status' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Build and Test (8.0.x, ubuntu-latest): REMS.Models/Review/ReviewResponseModel.cs#L5
Non-nullable property 'Review' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Build and Test (8.0.x, ubuntu-latest): REMS.Models/Appointment/AppointmentDetail.cs#L27
Non-nullable property 'appointmentDetails' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Build and Test (8.0.x, ubuntu-latest): REMS.Models/Review/ReviewListResponseModel.cs#L7
Non-nullable property 'DataList' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Build and Test (8.0.x, ubuntu-latest): REMS.Models/Review/ReviewListResponseModel.cs#L9
Non-nullable property 'PageSetting' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Build and Test (8.0.x, ubuntu-latest): REMS.Models/Client/ClientListResponseModel.cs#L13
Non-nullable property 'DataLst' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Build and Test (8.0.x, windows-latest): REMS.Models/Transaction/TransactionResponseModel.cs#L13
Non-nullable property 'Transaction' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Build and Test (8.0.x, windows-latest): REMS.Models/Transaction/TransactionResponseModel.cs#L14
Non-nullable property 'Client' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Build and Test (8.0.x, windows-latest): REMS.Models/Transaction/TransactionResponseModel.cs#L15
Non-nullable property 'Property' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Build and Test (8.0.x, windows-latest): REMS.Models/Transaction/TransactionRequestModel.cs#L17
Non-nullable property 'Status' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Build and Test (8.0.x, windows-latest): REMS.Models/Transaction/TransactionModel.cs#L17
Non-nullable property 'Status' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Build and Test (8.0.x, windows-latest): REMS.Models/Review/ReviewResponseModel.cs#L5
Non-nullable property 'Review' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Build and Test (8.0.x, windows-latest): REMS.Models/Appointment/AppointmentDetail.cs#L27
Non-nullable property 'appointmentDetails' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Build and Test (8.0.x, windows-latest): REMS.Models/Client/ClientListResponseModel.cs#L13
Non-nullable property 'DataLst' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Build and Test (8.0.x, windows-latest): REMS.Models/Client/ClientListResponseModel.cs#L14
Non-nullable property 'PageSetting' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Build and Test (8.0.x, windows-latest): REMS.Models/Jwt/JwtTokenModel.cs#L5
Non-nullable property 'Issuer' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Build and Test (6.0.x, windows-latest): REMS.Models/Transaction/TransactionResponseModel.cs#L13
Non-nullable property 'Transaction' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build and Test (6.0.x, windows-latest): REMS.Models/Transaction/TransactionResponseModel.cs#L14
Non-nullable property 'Client' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build and Test (6.0.x, windows-latest): REMS.Models/Transaction/TransactionResponseModel.cs#L15
Non-nullable property 'Property' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build and Test (6.0.x, windows-latest): REMS.Models/Transaction/TransactionRequestModel.cs#L17
Non-nullable property 'Status' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build and Test (6.0.x, windows-latest): REMS.Models/Appointment/AppointmentDetail.cs#L27
Non-nullable property 'appointmentDetails' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build and Test (6.0.x, windows-latest): REMS.Models/Transaction/TransactionModel.cs#L17
Non-nullable property 'Status' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build and Test (6.0.x, windows-latest): REMS.Models/Review/ReviewResponseModel.cs#L5
Non-nullable property 'Review' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build and Test (6.0.x, windows-latest): REMS.Models/Client/ClientListResponseModel.cs#L13
Non-nullable property 'DataLst' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build and Test (6.0.x, windows-latest): REMS.Models/Client/ClientListResponseModel.cs#L14
Non-nullable property 'PageSetting' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Build and Test (6.0.x, windows-latest): REMS.Models/Jwt/JwtTokenModel.cs#L5
Non-nullable property 'Issuer' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Code Scanning
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-java@v3, actions/checkout@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/