New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v1 documentation #134
Comments
Well, you're right about most of them, except number 6. I simply removed a constant called Some other things are:
|
It looks like |
Ahh yes. This is still being worked on and I'm thinking of more ways to make it efficient. I'm thinking maybe: // Can be called anything
instance.methods.foo();
// Cannot conflict with internal methods/properties
instance.foo(); |
And |
Yup @Bampye. It was just syntactic sugar for setting a DOM property. You can now manually set it with: <div m-literal:innerHTML.dom="rawHTML"></div> |
Another thing: // Shallow merge with data and notifies observer
instance.set({
foo: true,
bar: [1, 2, 3]
}); |
It seems component slot is breaking. |
@rizkyramadhan They were replaced by an insert system (to not collide with web components). So slots are now replaced with |
In regards to that |
DOM properties are now set with a new directive: These both were added in e620897. |
Moon v1 has branched off further than what is discussed here. Refer to the new docs. |
Until all the beautiful docs are updated, I figure it would be nice to have a place where the core breaking changes are documented.
So far from looking at commits since mid August, I've observed the following:
Moon.component
is nowMoon.extend
el
, it isroot
when creating a moon appm-model
attribute, it is now namedm-bind
$children
now use a version without$
SVG
instead ofisSVG
TEXT_TYPE
, but now the shorter literal"#text"
is usedThere's a couple things that I don't quite know about, like
dynamic
andfunctional
when it comes to component things.What other bumps are there in transitioning?
The text was updated successfully, but these errors were encountered: