-
-
Notifications
You must be signed in to change notification settings - Fork 234
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[9.6] Event Architecture #589
Conversation
Deploying with Cloudflare Pages
|
6dd720c
to
2c62c78
Compare
Codecov Report
@@ Coverage Diff @@
## master #589 +/- ##
===========================================
Coverage 100.00% 100.00%
- Complexity 511 528 +17
===========================================
Files 77 83 +6
Lines 1576 1606 +30
===========================================
+ Hits 1576 1606 +30
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
The implementation is blocked by the framework. The committing event is missing. |
The lock is released, the event has appeared in the framework. PR needs to be improved. |
2c62c78
to
696dbb7
Compare
3a67102
to
267e5b1
Compare
87f81a0
to
3584c5a
Compare
I will have to pull classes in events from app(). The octane issue will most likely go away. |
Thanks to the new functionality in the laravel framework (adding a committing event), it became possible to solve all the old problems of the package. And this is full support for laravel nova. The package actively helps you deal with the race condition. Before version 9.6, only with the help of AtomicServiceInterface it was possible to block the wallet for the duration of useful work, and later apply or roll back the transaction, but now the package implements lazy locks. When you work with the wallet API, your wallet is blocked until the commit/rollback operation.
The most important change is the check for the start of a transaction has been removed. Inside the package, I completely abandoned the custom solution for creating transactions.
Do not forget about the internal state, it is available exclusively in the AtomicServiceInterface. Those, the introduction of lazy locks does not negate the benefits of atomics. You can read more here: #562