Oh how I wish you could reference the current scope in JavaScript. The things you could do…
e.g., scope.someImport…
Oh how I wish you could reference the current scope in JavaScript. The things you could do…
e.g., scope.someImport…
Hmm… I think I might be able to create what I want by maintaining a component registry manually in my ES Module Loader and communicating it to the main process via an interprocess communication channel… but, yeah, being able to reference the current scope would be nice.
🤷♂️
(Basically, what I want is for Kitten¹ to be able to introspect the source code of a component, find the related components, and wire them up to handle events from the client (including garbage collection of listeners) without having to manually register the dependent component classes. Don’t Repeat Yourself and all that…)
Anyway… niche :)
@aral
I read "Kitten" as "Biden" and was like "dude, I don't think he can do that but also that's a very specific ask we're just trying to fight fascism here."
@DoesntExist Haha, oh the stuff I misread when I’m focussed on one thing or another sometimes :)
(Nope, because, of course, the actual reference doesn’t exist at the loader stage.)
Oh, well, I’m going to try and make it so that you’ll at least be able to connect child components in the markup itself so you don’t have to remember to do it in some other place. That should, at least, be doable.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.