Lots of warnings during compliation of JTE generated Kotlin code

After we have swithed to generate() in the build.gradle.kts (see our another issue #177), we are getting lots of Kotlin compiler warnings which we have never had before.

Below is list of warnings that we’ve faced:

// Unchecked cast: Any? to Response<ServiceResponse>
// many similar ones for different parameter names and types
// these all are our custom parameters which we pass into a KTE page, by declaring them like
// @param keyHistoryDetailsResponse: Response<KeyHistoryDetailsResponse>
    val fesServiceResponse = params["fesServiceResponse"] as Response<com.flowcrypt.eap.clients.fes.ServiceResponse>

// Parameter 'params' is never used
	@JvmStatic fun renderMap(jteOutput:gg.jte.html.HtmlTemplateOutput, jteHtmlInterceptor:gg.jte.html.HtmlInterceptor?, params:Map<String, Any?>) {
		render(jteOutput, jteHtmlInterceptor);
	}

// Parameter 'jteHtmlInterceptor' is never used
	@JvmStatic fun render(jteOutput:gg.jte.html.HtmlTemplateOutput, jteHtmlInterceptor:gg.jte.html.HtmlInterceptor?) {
		jteOutput.writeContent("....")
        }

// 'capitalize(): String' is deprecated. Use replaceFirstChar instead
       jteOutput.writeUserContent(provider.capitalize())

I suggest to add proper @Suppress(...) statements into the generated code. In the last case I’d suggest to use recommended method instead of deprecated one. On my end, I’m looking into how to disable such warnings for certain paths (generated code) in the project but no luck so far.

[IvanPizhenko]

Can you please also add in the beginning of each generated file following line:

@file:Suppress("ktlint")

I may later provide more fine-grained list of ktlint rules to disable, but for now suppressing all of them will be good enough.

[IvanPizhenko]

Thanks, found provider.capitalize() in my code, will fix it.