Sebastian Krüger

Thanks! That's kinda bad but understandable...

Why do you want a `?`. `name?` is not valid JavaScript so the error is expected...

That is not possible. All between {...} has to be valid JS. I never had user-provided templates. But you can create a list of valid fields where you can document...

Just looked at the timm code and a work around should be: ```js const additionalJsContext = { key: new Proxy({}, { set(obj, prop, value) { debug('set', {prop, value}) obj[prop] =...

I might have a solution for that... But that will not work in IE.

OK I wrote some prototype code: Let oldMerge be the current merge function and replace it with this new one. Did not test this code in any way so expect...

> And adjusted the recursive call in "get" and plugged in `proxyMerge`.. That is not needed (and will break). The error should be gone with that change and if not...

maybe ```ts get(_, key) { const obj = objects.filter(v=>v instanceof Proxy || key in v) if(obj.length === 0) return if(obj.lenght===1) return Reflect.get(obj[0], key, obj[0]) // Dont have to deal with...

Or instead of wrapping useing a proxy.

Got a small working prototype (all manual but can be automated): Assemblyscript ```ts export class Foo { constructor(public str: string) {} getString(): string { return this.str } } ``` Host:...