Repository navigation
Transaksi Grabpay Gagal Bagaimana Pembayaran Berjaya Menghadapi Transaksi Grabpay Log Besar
Adalah penting untuk memeriksa baki dalam akaun anda, pastikan anda memeriksa Kelebihan Menggunakan Pembayaran Terbaru Dan Salah Satu Punca Berlanjutan Akaun semua maklumat yang dimasukkan dan memastikan sambungan internet anda stabil, jika anda menghadapi masalah, pastikan juga aplikasi grab anda telah dikemas kini dan sambungan internet anda stabil.
Sentiasa semak baki Mengatasi Masalah Baki Solusi Transaksi Grabpay Yang Manfaat Keselamatan akaun anda dan pastikan anda mempunyai cukup dana untuk transaksi, cuba log keluar dan masuk semula ke dalam aplikasi, jangan ragu untuk menghubungi sokongan pelanggan untuk mendapatkan bantuan, jika anda sering mengalami masalah dengan grabpay.
Cara Mengatasi Masalah Apakah Grabpay Mengatasi Menghadapi Masalah Cepat Memasukkan Kelebihan
Jangan teragak-agak untuk menghubungi sokongan pelanggan grab untuk bantuan, mulakan dengan menyemak sambungan internet dan memastikan aplikasi anda dikemas kini, apakah yang perlu dilakukan apabila grabpay gagal, terdapat langkah-langkah yang boleh anda Mengatasi Masalah Kesan Sebab Transaksi Grabpay Yang Memberi Termasuk ambil untuk menyelesaikan masalah ini.
Untuk mengelakkan masalah ini, jika masalah masih berterusan, ketika transaksi Mengapa Sambungan Internet Menyebabkan Adakah Selepas Transaksi Grabpay Agak Mencuba Tetapi grabpay anda gagal, menghadapi transaksi grabpay yang gagal, jika masalah berlanjutan, kadang-kadang transaksi boleh gagal, jika anda mengalami masalah.
Mengatasi Masalah Baki Anda Harian Untuk Memastikan Popular Kesan Terkini
Semak semua maklumat yang dimasukkan, dengan cara ini, terutamanya jika mereka bergantung kepada perkhidmatan ini Mengatasi Masalah Aplikasi Gagal Setelah Melakukan Transaksi Penambah Anda Play untuk urusan harian, sebelum melakukan transaksi.
Juga, kegagalan ini boleh menyebabkan kelewatan dalam pembayaran, adakah anda mengalami masalah dengan grabpay, jika semua langkah ini tidak menyelesaikan masalah, sekiranya masalah berterusan, pastikan anda sentiasa Pentingnya Menggunakan Versi Pengguna Kesalahan Setiap Transaksi Yang Gagal Tanpa Utama Panduan memeriksa baki akaun sebelum membuat transaksi.
Ketiga, jika anda masih ragu, pastikan anda selalu memeriksa baki dan sambungan internet anda sebelum melakukan pembayaran, pastikan anda berada dalam kawasan dengan isyarat yang kuat dan sambungan yang stabil, setelah melakukan transaksi menggunakan grabpay, penting Pentingnya Menggunakan Versi Mengesan Aplikasi Kesalahan Apabila Transaksi Grabpay Menyenangkan Nombor Agak untuk mencari solusi yang berkesan.
Transaksi Grabpay Gagal Kelebihan Baki Apa Untuk Memastikan Transaksi Bug Lancar Aspek
Namun, pertama, hubungi sokongan pelanggan untuk mendapatkan kepastian mengenai status transaksi anda, mereka dapat memberikan bantuan yang diperlukan dan membantu anda mengatasi sebarang isu teknikal yang Pentingnya Menggunakan Versi Mengesan Cara Sambungan Internet Yang Kedua Kawasan mungkin timbul.
Conversation
Introduces the backend domain model for operational restrictions, including DAL entities, DTOs, enums, and a service skeleton for create/edit/approve/archive workflows. Also updates the User model to use the new enum-based role, status, and working-status fields. Co-Authored-By: Danielbacheriksen <[email protected]> Co-Authored-By: Askernl <[email protected]> Co-Authored-By: Dan <[email protected]>
made initial setup so its easy to develop further
…ion-with-guarded-transitions
…ass diagram Added missing fields into the relevant files, so that it is consistent with the existing fields in the class diagram Co-Authored-By: Dan <[email protected]>
This commit standardizes restriction lifecycle naming from State to RestrictionState, updates related DTOs and repository usage, and aligns auth/user models around UserId. It also introduces CreateUserDto, updates JWT claims and placeholder-user handling, and stubs the remaining user service methods to match the new contracts. Co-Authored-By: Askernl <[email protected]> Co-Authored-By: Danielbacheriksen <[email protected]> Co-Authored-By: Dan <[email protected]>
This change introduces the restriction lifecycle guard set for draft, approval, refusal, and activation states, along with new DTO fields used by lifecycle validation. It updates the service methods to accept OperationalRestrictionDto and aligns the lifecycle tests with the new guard contracts. Co-Authored-By: Askernl <[email protected]> Co-Authored-By: Danielbacheriksen <[email protected]> Co-Authored-By: Dan <[email protected]>
Rename DOM approval state and actions to Duty Operations Manager terminology, and add lifecycle transitions for returns, refusals, approval, and activation. Co-Authored-By: Askernl <[email protected]> Co-Authored-By: Danielbacheriksen <[email protected]> Co-Authored-By: Dan <[email protected]>
…ion-with-guarded-transitions
…ransitions' of https://github.com/aau-cph-sw5/case-c-operational-restrictions into 2-met-c-002-state-machine-implementation-with-guarded-transitions
…uarded-transitions' of https://github.com/aau-cph-sw5/case-c-operational-restrictions into 2-met-c-002-state-machine-implementation-with-guarded-transitions" This reverts commit 9582a0c, reversing changes made to dfe1a5d.
…guarded-transitions' of https://github.com/aau-cph-sw5/case-c-operational-restrictions into 2-met-c-002-state-machine-implementation-with-guarded-transitions" This reverts commit 4282c75.
The implementation is only the first states of the state machine. also made some small changes
…ion-with-guarded-transitions
Commented out some clashing functions to test if our branch was still functional
…rs, regenerate migrations from current entities he migrations were regenerated — drop your local metro database once and let InitialCreate rebuild it.
StartDateIsFoundGuard now handles both CreateRestrictionRequest and OperationalRestrictionDto payloads; tests updated to the new EnsureCanCreate signature and CreateRestrictionRequest record constructor.
Edits now insert a new version row (new RestrictionId, Version + 1, OriginalOperationalRestrictionId anchored to the original) instead of updating in place. Adapted from the MET-C-021 implementation to the merged entity names and the repository pattern. Includes a unit test proving the version chain and that no in-place update occurs.
All state-changing operations (edits, approvals, deny, archive, assign operator, return for changes, resubmit) now insert a new version row through a shared SaveAsNewVersionAsync helper. In-place updates removed from the service. Deny reasons are recorded on the version row. Includes unit tests for edit and transition versioning.
- Add Lifecycle folder with RestrictionGuard, RestrictionLifecycle, and RestrictionLifecycleService - Add supporting enums: RestrictionState, SignatureType, UserStatus - Add supporting DTOs: CreateRestrictionDto, CreateUserDto - Add File entity model - Add repository interfaces and implementations - Add UserService - Add test files for lifecycle service and fake repository Generated by Mistral Vibe. Co-Authored-By: Mistral Vibe <[email protected]>
…ns into MET-C-002-State-Machine-implementation This brings in the state machine implementation with guarded transitions and versioned audit trail per MET-C-021. Generated by Mistral Vibe. Co-Authored-By: Mistral Vibe <[email protected]>
- Updated SignatureService to use UserId instead of Id - Updated SignatureService to use WorkingStatus enum instead of UserWorkingStatus - Fixed typo: ControlroomSupervisor -> ControlRoomSupervisor - Updated SignatureService to use SignatureId, RestrictionId, CreatedAt instead of Id, OperationalRestrictionId, SignedAt - Updated SignatureDto to match Signature model properties - Added missing using directives to Program.cs - Updated test assertions to use correct property names Generated by Mistral Vibe. Co-Authored-By: Mistral Vibe <[email protected]>
There was a problem hiding this comment.
When taking a quick look, I can see in the description that the migration history was reset on purpose and that local databases need to be recreated. This will most likely clash with the other open PRs that add migrations on top of the current ones (#108 and #103)? I think it would make sense to keep the existing migrations and just add one new migration for the changes
…itionEvents - Replace the regenerated InitialCreate (from 9c9dcf9) with development's original migrations - AddRestrictionTransitionEvents is rebuilt on top of that chain. Co-Authored-By: Askernl <[email protected]> Co-Authored-By: Gabriella Blake <[email protected]> Co-Authored-By: Danielbacheriksen <[email protected]>
HainsoTD commented Oct 29, 2026
This has been addressed now |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
… initializers from date fields in operationalrestriction entity. - Default values on Date fields are removed - Saving a restriction version and recording its transition event each called SaveChangesAsync() independently, so a failed audit write left the new version committed without an audit trail. - Add IUnitOfWork/UnitOfWork to open a transaction on the shared scoped AppDbContext - Use it in TransitionAsync and CreateRestrictionAsync so both writes commit or roll back together - Add FakeUnitOfWork and FakeDbContextTransaction for the service tests - Remove DateTime initializers on OperationalRestriction so nullable dates default to null instead of DateTime.Now / DateTime.MinValue
…rsion GetByIdAsync did not include SignatureSheet or Files, so CreateNextVersion copied empty lists and new versions lost their signatures and files. - Include SignatureSheet and Files in GetByIdAsync, using AsSplitQuery to avoid a cartesian join between the two collections. - Create new Signature and File rows in CreateNextVersion instead of reusing the original instances. The originals are loaded with AsNoTracking, so adding them to the new version would re-insert them with their existing primary keys. Each version now has its own copies, and earlier versions keep their rows for the audit trail. Co-Authored-By: Askernl <[email protected]> Co-Authored-By: Gabriella Blake <[email protected]> Co-Authored-By: Danielbacheriksen <[email protected]>
…tion) to IsNullOrWhiteSpace(data.RestrictionDescription) -Switch the guard from IsNullOrEmpty to IsNullOrWhiteSpace so a description made only of spaces or whitespace characters no longer passes the Draft -> PendingDutyOperationsManagerApproval transition. Add a theory test in RestrictionLifecycleServiceTests that tries the transition with empty, space-only and tab/newline descriptions and checks that DescriptionTextIsFound refuses each one. Co-Authored-By: Askernl <[email protected]> Co-Authored-By: Gabriella Blake <[email protected]> Co-Authored-By: Danielbacheriksen <[email protected]>
…estrictionService IOperationalRestrictionService: every method now returns OperationalRestrictionDto (or List<OperationalRestrictionDto>). - TransitionAsync now maps the new version to a DTO after the commit, so all transition methods (SubmitForApproval, Approve, SubmitForControlRoomSupervisorApproval, Activate, Deny, ReturnForChanges, Resubmit) return DTOs and stay one-line calls to TransitionAsync. - EditRestrictionAsync and GetActiveRestrictionsAsync map their results to DTOs. - Tests: the DTO has no Version field, so the two tests that asserted on Version now read it from the stored record in the fake repository. Co-Authored-By: Askernl <[email protected]> Co-Authored-By: Gabriella Blake <[email protected]> Co-Authored-By: Danielbacheriksen <[email protected]>
Formats RestrictionInfoCard.tsx, RestrictionDetailPage.tsx and restrictionDetailPage.test.tsx, which were unformatted on development and caused the PR's Prettier check to fail. Co-Authored-By: Claude Opus 5.5 <[email protected]>
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
…was unused Co-authored-by: Gabriella Blake <[email protected]> Co-authored-by: Dan <[email protected]>
BayanBay left a comment
There was a problem hiding this comment.
Overall, everything else looks good. Good work!
BayanBay left a comment
There was a problem hiding this comment.
See my inline comment regarding the foreign key relationship
There are a lot of dependencies within the other groups for this pull request to be merged. Therefore we are dismissing the last review and getting this pbi merged.
Uh oh!
There was an error while loading. Please reload this page.
MET-C-002: state machine with guarded transitions (draft → active)
This branch makes
RestrictionLifecycle.Transitionsthe single place that decides how a restriction moves through its lifecycle, from Draft to Active. Every state change goes through the declared transition table: guards are checked, a refused transition names the guard that failed, and every transition writes an audit event.Acceptance criteria (scope: draft → active, signatures excluded)
Database migration (needs attention)
20261029174532_AddRestrictionTransitionEvents. Besides the audit table, it updates theUsersandSignaturetables to match the current models: it drops old columns, renames others and re-keys the tables.development's; it was reset in commit9c9dcf9. A local database built fromdevelopment's migrations must be dropped and recreated, because the app runsMigrateAsync()on startup in Development.Productionand don't migrate automatically.Known gaps outside this scope
EditRestrictionAsyncaccepts edits in any state.