-
Business Reason
Our current implementation is that transaction "families" must share itemization logic. If one is itemized, all are itemized, and if one is unitemized, all are unitemized. **This is i…
-
I will be nice if the book will have a section that show how to use yii\di\Container and how it can help to decouple the business logic from the framework.
-
They overlap significantly so they should be made a little dry since this is complicated business logic and don't want to maintain it in multiple places and the objects they are acting on are the same…
-
Thanks so much guys for creating this. It makes my business logic so much better. Keep it up!
(There were no Github discussions, so I figured I'd throw it here).
-
One source of truth with actual configuration.
**Advantages**
1) More readable business logic without many checks and reads from `process.env`
2) Minimize risks of human error
-
As the product owner,
I want the code in the repo to be bulletproof
And have the business logic covered by unit tests
So that other people can actually use it
-
Here's an extension function that might be useful to include.
```kotlin
/**
* Maps this [Result][Result] to [Result][Result] by either applying the [transform]
* function to the [value][Ok.val…
-
Currently I believe the entry point for the GUI is the GUITest class, which obviously isn't where it needs to go eventually.
We will ultimately need several different entry points, the first being fo…
-
Capturing carry over tasks for Returns work:
- [x] #3504
- [ ] #3188
- [x] #3332
- [x] #3286
- [x] #3331
- [x] #3315
- [ ] Columns in both the detail view and the edit modal were minima…
-
Ideally we don't want to be calling out to the shell to perform part of the business logic. This should be translated to Clojure, using whatever libraries are appropriate for Git and file system.