it works with everything except events, because events have a slightly different meaning for components vs elements
it also doesn't work for binding attributes like twoway and lazy
for events, I usually surface everything I think we'll be relevant inside the component or macro and leave it up to the use site which ones are consumed
it also doesn't work for binding attributes like twoway and lazy
for events, I usually surface everything I think we'll be relevant inside the component or macro and leave it up to the use site which ones are consumed
I just merged a doc fix, so maybe the deploy is busted
I'll poke around a bit
I'll poke around a bit
the gh pages site is trying to redirect there atm too
gh pages seems to be having some weirdness in general
s back
I guess that's the downside of depending on other services... you don't have to maintain them, but when something breaks, there's almost nothing you can do
Hey sooo, if I wanted to suggest a change to the website tutorial page (https://ractive.js.org/tutorials/hello-world/), where would I do it?
Looks like it's here: https://github.com/ractivejs/ractivejs.github.io/blob/dev/docs/tutorials/hello-world.md
I mean in the javascript code. In step 3, the three "run it" buttons change the output in the playground. When the third button is clicked, it changes the name and greeting to mandarin, when the second button is clicked, it should just change the name, however, it changes the greeting as well. Same for the first button. I think it would be better if they just changed what they should change.
It looks like the JavaScript that actually gets run is in the
data-eval attribute. For example, just above the ractive.set('name', 'tout le monde'); in hello-world.md there's "E4QwxgLglgbgpgOgM5wgCgOQHNh1VAOywwBoACDAIQHsCAragV2AwEoBuAKFElkRXQYCIALZxSFCEwhkANnDIjaAE3EcgA", which lzString.decompressFromEncodedURIComponent() returns as "ractive.set('greeting', 'Bonjour');\nractive.set('name', 'tout le monde');". Unfortunately, just changing that data-eval attribute to have this: E4QwxgLglgbgpgOgM5wgCgOQDsQFs4YA0ABBhAPYCuExANnMbuVgCYECUA3EA (for it to only change the name and not the greeting) is not sufficient, since it looks like the data-runtutorial attribute is used to reset the whole playground, so then the output becomes Hello, tout le monde!, which is also not what we want. I don't know the right way to fix this.
plugin config is essentially
ractive({
outputExtension: '.ts',
autoExport: true,
outputDir: './client/.views/',
}),
typescript({
tsconfig: './client/tsconfig.json',
}),
for most projects, I have a separate view watcher based on nodemon that runs the ractive bin in incremental mode and dumps output into a dir that rollup is watching
I started a gh discussion on it with my watch helper here: https://github.com/ractivejs/ractive/discussions/3405
it's a bit more involved than I'd like it to be, but it works well enough
the keys and values are both strings, so I don't need to use a JS Map here, but I was mostly curious.
Does Ractive have a supported way to get just the
Here's an example:
extra-attributes as an object?Here's an example:
<sweetComponent
foo="hello"
bar="world"
baz="i am extra"
qux="also extra"
></sweetComponent>const sweetComponent = Ractive.extend({
isolated: true,
attributes: {
required: [ 'foo', 'bar' ],
optional: [],
},
oninit() {
// can i get *just* extra-attributes some how?:
//{ baz: 'i am extra', qux: 'also extra' }
},
})
If not I think I can just do
mapAll as true on the attributes and then filter off all of the explicitly required or optional ones.
How very Svelte of it.