Jan Biedermann
Jan Biedermann
using `state foo: 12` at class level from lap20 onwards sets state synchronously nicely without causing a second render. using implicit state at instance level may cause a second render...
For clarification: `after_error` is currently implemented as a callback like `before_mount` or `after_mount` `on(:loading)`currently is not a event but a condition/state, the resembling events would have to be: `on(:loading_started)` and...
behaviour is fixed the 1.0.0 laps no deprecation warning has been added it should be documented that callbacks receive ruby hashes as args
now a user reports a problem. to check you need to know all versions of all gems, maybe, depending on the depth of the problem, and verify. I prefer the...
I understand your concern, i agree, if somebody wants to run production like this, the versioning needs to be relaxed.
esbuild prints warnings about eval() when bundling opal code. They suggest Function too. They suggest 2 alternatives: https://esbuild.github.io/content-types/#direct-eval
What about: ```ruby o = Object.new m = 'to_s' o.send(m) ``` ?
See #2569