Why isn't this a valid js syntax? Any way around it without having to manually type it out ```fun g...

# react

[Nikola Milovic]

Why isn't this a valid js syntax? Any way around it without having to manually type it out

fun getDefaultValuesFromProfile(profile: ProfileModel): dynamic {
    val d : dynamic = js("{ defaultValues : {...profile}}")
    return d
}

Which should be totally valid in ts (javascript)

function test(profile: IProfile) {
  const test = { defaultValues: { ...profile } };
}

[CLOVIS]

What is the error message?

[Nikola Milovic]

Invalid js syntax @CLOVIS , in the IDE

[CLOVIS]

Is that an IDEA warning, a compilation error, or a runtime error?

[Nikola Milovic]

@CLOVIS IDE error and when compiling I get

> Task :web-app:compileDevelopmentExecutableKotlinJs FAILED
e: org.jetbrains.kotlin.com.google.gwt.dev.js.parserExceptions.JsParserException: syntax error at (0, 19)

With

fun getDefaultValuesFromProfile(profile: ProfileModel): dynamic {
    val d: dynamic = js("{ defaultValues : {...profile}}")

[turansky]

Common recomendations:
1. Avoid dynamic
2. Avoid js calls
First step:

fun getDefaultValuesFromProfile(profile: ProfileModel): dynamic {
    return jso {
        defaultValues = Object.clone(profile)
    }
}

Second step:
Strict contracts, using external interfaces

[Nikola Milovic]

@turansky thanks, yeah I'll have to focus a bit more on my library wrappers. I'll probably post a separate question related to that as I've had some issues getting it to work with interfaces and types. This is kinda hacky to get it to work for now

[turansky]

I know one “legal” js call - js("({})")

In most cases you can describe types without dynamic usages

Typical solutions you can find in:
1. Wrappers
2. Modern examples. Latest practices you can find here