Extending with JS: Object access within DynamicModel not ergonomic?

[niravcodes]

Extending with JS: Object access within DynamicModel not ergonomic?

[ganigeorgiev]

I'm not sure that I understand what actually is the issue or the expected behavior.

If the problem is that access to the the custom map is not ergonomic then I don't know an easy solution for this without forking goja.

You can also check:

• https://pkg.go.dev/github.com/dop251/goja#hdr-Maps_with_methods
• https://pocketbase.io/docs/js-overview/#engine-limitations
• #2825 (comment) (general overview how the goja integration works)

If you want to access the body parameters as a plain map an alternative could be:

const data = $apis.requestInfo(c).data

console.log(data)

If you think that this can be improved, feel free to create a POC implementation and I'll try to review it but note that the routing will change with the next release as part of #4355.

If you have other question, please open a Q&A discussion as the threaded format is more suitable for this.

[niravcodes]

const data = $apis.requestInfo(c).data is exactly what I was looking for. Thanks :)