-
Notifications
You must be signed in to change notification settings - Fork 341
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
KTOR-4082 Add native image sample with config file #195
Conversation
@@ -0,0 +1,35 @@ | |||
|
|||
val kotlin_version: String by project |
Check warning
Code scanning / detekt
Variable names should follow the naming convention set in the projects configuration. Warning
@@ -0,0 +1,35 @@ | |||
|
|||
val kotlin_version: String by project | |||
val logback_version: String by project |
Check warning
Code scanning / detekt
Variable names should follow the naming convention set in the projects configuration. Warning
@@ -0,0 +1,13 @@ | |||
package example.com | |||
|
|||
import example.com.plugins.* |
Check warning
Code scanning / detekt
Wildcard imports should be replaced with imports using fully qualified class names. Wildcard imports can lead to naming conflicts. A library update can introduce naming clashes with your classes which results in compilation errors. Warning
package example.com | ||
|
||
import example.com.plugins.* | ||
import io.ktor.server.application.* |
Check warning
Code scanning / detekt
Wildcard imports should be replaced with imports using fully qualified class names. Wildcard imports can lead to naming conflicts. A library update can introduce naming clashes with your classes which results in compilation errors. Warning
@@ -0,0 +1,14 @@ | |||
package example.com.plugins | |||
|
|||
import io.ktor.server.application.* |
Check warning
Code scanning / detekt
Wildcard imports should be replaced with imports using fully qualified class names. Wildcard imports can lead to naming conflicts. A library update can introduce naming clashes with your classes which results in compilation errors. Warning
@@ -0,0 +1,18 @@ | |||
package example.com.plugins | |||
|
|||
import io.ktor.serialization.kotlinx.json.* |
Check warning
Code scanning / detekt
Wildcard imports should be replaced with imports using fully qualified class names. Wildcard imports can lead to naming conflicts. A library update can introduce naming clashes with your classes which results in compilation errors. Warning
package example.com.plugins | ||
|
||
import io.ktor.serialization.kotlinx.json.* | ||
import io.ktor.server.application.* |
Check warning
Code scanning / detekt
Wildcard imports should be replaced with imports using fully qualified class names. Wildcard imports can lead to naming conflicts. A library update can introduce naming clashes with your classes which results in compilation errors. Warning
|
||
import io.ktor.serialization.kotlinx.json.* | ||
import io.ktor.server.application.* | ||
import io.ktor.server.plugins.contentnegotiation.* |
Check warning
Code scanning / detekt
Wildcard imports should be replaced with imports using fully qualified class names. Wildcard imports can lead to naming conflicts. A library update can introduce naming clashes with your classes which results in compilation errors. Warning
import io.ktor.serialization.kotlinx.json.* | ||
import io.ktor.server.application.* | ||
import io.ktor.server.plugins.contentnegotiation.* | ||
import io.ktor.server.response.* |
Check warning
Code scanning / detekt
Wildcard imports should be replaced with imports using fully qualified class names. Wildcard imports can lead to naming conflicts. A library update can introduce naming clashes with your classes which results in compilation errors. Warning
import io.ktor.server.application.* | ||
import io.ktor.server.plugins.contentnegotiation.* | ||
import io.ktor.server.response.* | ||
import io.ktor.server.routing.* |
Check warning
Code scanning / detekt
Wildcard imports should be replaced with imports using fully qualified class names. Wildcard imports can lead to naming conflicts. A library update can introduce naming clashes with your classes which results in compilation errors. Warning
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, just a few suggestions for the README.
Co-authored-by: Vik Nikolova <[email protected]>
Co-authored-by: Vik Nikolova <[email protected]>
Fix KTOR-4082 GraalVM: Native image with HOCON server sample