ChristophP
ChristophP
I'm having a similar problem where I want to pass the table name and columns to a copy query dynamically. ```js const query = sql`COPY ${tableName} ${columns} FROM STDIN`; ```...
@porsager I tried this ```js sql`COPY ${ sql('users') } ${ sql(['peter', 'assi']) } FROM STDIN` ``` but I got "Could not infer helper mode".
Nesting `sql.unsafe()` is not something that's supported yet is it? I tried it on a copy query like this. ```js const cols = `(col1, col2)`; sql`COPY some_table ${sql.unsafe(cols)} FROM STDIN`;...
@janwirth great to have some contribution in this direction. Two questions: 1. How would subscriptions be unbound and event handlers removed? (I see you still have a WIP in the...
I actually found out that leaking stuff is not necessarily specific to multiple elm apps on the page, but more to reinitializing elm modules(calling `Elm..embed/fullscreen()`). This can happen for example...
@joefiorini I haven't thought of using web components callbacks yet but nice idea. I have been using something similar with ports and callbacks to clean up lingering subscriptions. But it...
@FranzSkuffka Yup
I just came up with another reason why a stop, unsubscribe, destroy mechanism for an elm app/element would be good: **the debugger** The debugger records a history of all events...
So all in all what a `app.kill/app.destroy` should do to accomodate the scenarios for mulitple `Browser.element`s on the page: 1. remove all subscriptions 2. kill the debugger/clear it's history 3....
Very interesting. And thanks for sharing the gist.