31 Commits (7fbb71a7886245a9564ce7a82d64e3b35c0a9c37)

Author	SHA1	Message	Date
Rich Harris	1f46e23e1b	More conservative invalidation	6 years ago
Conduitry	df57e508f8	use extension-less import for svelte/internal	6 years ago
Rich Harris	f45e2b70fd	Implement reactive assignments (#1839) ... This also includes elements of RFCs 2 and 3	6 years ago
Rich Harris	e5ae97b9c9	use helper for combining window binding props	6 years ago
Rich Harris	4afa133214	reinstate tests	6 years ago
Rich Harris	4a88c9ccb5	remove -bundle files	6 years ago
Rich Harris	a18cec0ec6	not sure where that extra blank line came from	6 years ago
Rich Harris	c2f0ca3e2e	alternative approach to #1520	6 years ago
Jacob Wright	2c24c36120	Allows fragment updates to happen after state updates ... Proposed fix for #1520. Provides a starting point for discussion.	6 years ago
Rich Harris	3778431775	Merge pull request #1670 from sveltejs/init ... Share more init work	6 years ago
Rich Harris	d323f51e6c	update tests	6 years ago
Jacob Wright	b6e51ddc32	Change actions to init on mount rather than hydrate ... Looking at the discussion on https://github.com/sveltejs/svelte/pull/1247 it sounds like this was the intended way actions would be set up to work (which is why we didn't add a `mount` lifecycle method). I *believe* this is a fix in the original implementation. Complaints in chat about this surfaced the issue. Some libraries expect the element to be in the DOM when initializing and these libraries cannot be used without any lifecycle hook. @PaulMaly is requesting this be looked at, and I agree with his assesment. What's more, this change *should* be backwards compatable. Actions which work before this change should continue working after this change.	6 years ago
Rich Harris	b94d7adfec	replace appendNode(node, parent) with append(parent, node) - easier to follow	6 years ago
Conduitry	e66d9ffae7	in .fire always set calling flag back to false (#1587) ... * in .fire always set calling flag back to false (#1573) * update expected bundles	6 years ago
Pavel Malyshev	52ece0b5f0	Fix for #1538	6 years ago
Rich Harris	c4937d271f	fix skipped intros	7 years ago
Rich Harris	042ec54f7f	nested component transitions	7 years ago
Rich Harris	44bb2da29b	add skipIntroByDefault compiler option (#547)	7 years ago
Rich Harris	103f278cfc	update tests	7 years ago
Rich Harris	a29e2733cd	update tests	7 years ago
Rich Harris	ef39f00902	assign custom methods to custom element prototype - fixes #1369	7 years ago
Rich Harris	86d3476b55	minor fixes, update various tests	7 years ago
Rich Harris	f8b076b2f3	set state to blank object on destroy, not null - fixes #1354	7 years ago
Rich Harris	df4e3678dc	update snapshot tests	7 years ago
Rich Harris	daa2635cd3	update snapshot tests	7 years ago
Rich Harris	c1573dbf2c	implement onstate and onupdate	7 years ago
Rich-Harris	36290cb6cd	component spread	7 years ago
Rich Harris	c9435fc87f	Merge pull request #1279 from jacwright/action-this ... Make actions execute with the component context	7 years ago
Luke Edwards	a412f11907	update test samples’ expectants	7 years ago
Jacob Wright	9b0a884035	Make actions execute with the component context	7 years ago
Jacob Wright	04f5d5c975	Adds actions to components ... Actions add additional functionality to elements within your component's template that may be difficult to add with other mechanisms. Examples of functionality which actions makes trivial to attach are: * tooltips * image lazy loaders * drag and drop functionality Actions can be added to an element with the `use` directive. ```html <img use:lazyload data-src="giant-photo.jpg> ``` Data may be passed to the action as an object literal (e.g. `use:b="{ setting: true }"`, a literal value (e.g. `use:b="'a string'"`), or a value or function from your component's state (e.g. `add:b="foo"` or `add:b="foo()"`). Actions are defined in a "actions" property on your component definition. ```html <script> export default { actions: { b(node, data) { // do something return { update(data) {}, destroy() {} } } } } </script> ``` A action is a function which receives a reference to an element and optionally the data if it is added in the HTML. This function can then attach listeners or alter the element as needed. The action can optionally return an object with the methods `update(data)` and `destroy()`. When data is added in the HTML and comes from state, the action's `update(data)` will be called if defined whenever the state is changed. When the element is removed from the DOM `destroy()` will be called if provided, allowing for cleanup of event listeners, etc. See https://github.com/sveltejs/svelte/issues/469 for discussion around this feature and more examples of how it could be used.	7 years ago