-
Updated
Mar 2, 2022 - JavaScript
clean-architecture
Here are 4,407 public repositories matching this topic...
-
Updated
Mar 12, 2022 - C#
-
Updated
Mar 20, 2022
-
Updated
Mar 22, 2022 - C#
I believe the comparison operator used in the IsBroken
method is wrong because the rule is checking that meeting attendees limit must be greater than guests limit.
-
Updated
Jun 9, 2020 - Go
-
Updated
Mar 17, 2022 - Kotlin
-
Updated
Mar 20, 2022 - TypeScript
-
Updated
Mar 17, 2022 - C#
-
Updated
Mar 2, 2022 - C#
-
Updated
Feb 18, 2022 - Kotlin
-
Updated
Oct 30, 2021 - Kotlin
-
Updated
Mar 21, 2022 - Swift
-
Updated
Nov 2, 2021 - Swift
Let's add MinVer and on successful builds generate a release.
-
Updated
Dec 8, 2021 - TypeScript
-
Updated
Dec 4, 2019 - Java
-
Updated
Mar 10, 2022 - C#
-
Updated
Jan 26, 2022 - Go
Why not Hilt?
Why don't you use Hilt? Google says
Dagger and Hilt code can coexist in the same codebase. However, in most cases it is best to use Hilt to manage all of your usage of Dagger on Android.
-
Updated
Mar 11, 2022 - C#
We can replace getType()
and instead use an attribute on the collector
-tag for registering them in the Registry under that name.
The depfile itself will not change. We need to modify the service configuration in config/services.php (add attributes to tag, inject tagged collectors into Registry by name) and change the Registry itself by assuming the iterable has the type as key, i.e. somethi
I'd love to be able to get an ArgumentNullException when the value is null and a plain ArgumentException when it simply has some invalid form. My current best practice for this is:
Actions = Guard.Against.Inv
-
Updated
Nov 25, 2021 - C#
-
Updated
Jan 19, 2022
-
Updated
Feb 23, 2022 - Swift
-
Updated
May 10, 2021 - Kotlin
-
Updated
Mar 18, 2022 - C#
-
Updated
Feb 8, 2021
Improve this page
Add a description, image, and links to the clean-architecture topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the clean-architecture topic, visit your repo's landing page and select "manage topics."
This will help be explicit about which SDK version is expected, and should make CI/CD builds behave more consistently.