Backend-User
User micro service for backend of HRV-Mart (by HRV-Mart)
detekt
Static code analysis for Kotlin (by arturbosch)
Backend-User | detekt | |
---|---|---|
1 | 5 | |
1 | 6,053 | |
- | 1.1% | |
4.1 | 9.8 | |
10 months ago | 6 days ago | |
Kotlin | Kotlin | |
Apache License 2.0 | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Backend-User
Posts with mentions or reviews of Backend-User.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-08.
-
HRV-Mart
In order to create a scalable back-end I use micro-service architecture. Current version of HRV-Mart back-end consist of Product-Microservice, User-Microservice, Auth-Microservice, Order-Microservice, Cart-Microservice, Like-Micorservice and API-Gateway. Above micro-services are loosely couple and communication between them happens via Apache Kafka. In order to make them more secure, I added unit tests. The master branch is protected via branch protection rules
detekt
Posts with mentions or reviews of detekt.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-08.
-
HRV-Mart
In protection rules, I added build workflow in Require status checks to pass before merging. This is to ensure that before merging code in master branch, build should run successfully. I also added Jacoco Code Coverage to make sure that enough unit tests are available in project and Detekt to make sure that code in project is readable. I added them in build configuration. Even if one of them gives error, build will fail. Whenever, someone push code in pull request, build action will run and check if build is running successfully or not.
-
Modern Android Development in 2023
Detekt
- Change aware code analysis tools?
-
Supercharge your Kotlin Project
ext { // https://github.com/detekt/detekt/releases detektVersion = "1.17.0" } dependencies { classpath 'com.android.tools.build:gradle:7.0.0' classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:1.4.32" ## DETEKT DEPENDENCY classpath "io.gitlab.arturbosch.detekt:detekt-gradle- plugin:$detektVersion" }
-
Android Style Guide
I haven't looked through it completely, but have you considered adhering to detekt and ktlint as well?
What are some alternatives?
When comparing Backend-User and detekt you can also consider the following projects:
user-library
ktlint - An anti-bikeshedding Kotlin linter with built-in formatter
Backend-Cart - Cart micro-service for backend of HRV-Mart
sonarlint-intellij - SonarLint for IntelliJ
order-library - Library for Backend-Order
ktfmt-gradle - A Gradle plugin to apply ktfmt to your builds, and reformat you Kotlin source code like a glimpse 🧹🐘
Backend-Like - Like micro-service for HRV-Mart
dokka - API documentation engine for Kotlin
Backend-Order - Order mirco-service for HRV-Mart application
keplin - Secure Kotlin scripting and binary lambda-scripts
product - Product libray
KotlinW - A small wrapper for the Kotlin compiler that can be used to execute .kts scripts