29 Commits (5e0455bb791dccacf5ddeed5bc4af4e8b93d2c27)

Author	SHA1	Message	Date
Richard Harris	c3dfafa859	update tests	7 years ago
Richard Harris	a28badcc06	alternative fix for #3508	7 years ago
Rich Harris	bbad46a96b	Structured code generation (#3539)	7 years ago
Conduitry	348b8cde03	update tests (#1434) (#2935)	7 years ago
Rich Harris	8efa51519d	update API reference docs (#2206)	8 years ago
Rich Harris	7e8e891d91	Tidy up (#2252)	8 years ago
Richard Harris	20a4e5756c	update JS tests	8 years ago
Rich Harris	69c9422907	Better composition — implements https://github.com/sveltejs/rfcs/pull/12	8 years ago
Richard Harris	c464a11cdf	dont use identity function to reflect props	8 years ago
Rich Harris	c30ae9a896	Overhaul transitions - fixes #1906	8 years ago
Richard Harris	9cac743948	update tests	8 years ago
Rich Harris	b30f2cdbf1	More conservative invalidation	8 years ago
Conduitry	b84f1fb308	use extension-less import for svelte/internal	8 years ago
Rich Harris	efba821c84	Implement reactive assignments (#1839) ... This also includes elements of RFCs 2 and 3	8 years ago
Rich Harris	f385e829b7	use helper for combining window binding props	8 years ago
Rich Harris	d081e830c8	reinstate tests	8 years ago
Rich Harris	8fe75716a4	alternative approach to #1520	8 years ago
Jacob Wright	f39d026137	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.	8 years ago
Rich Harris	6df0aa7a18	replace appendNode(node, parent) with append(parent, node) - easier to follow	8 years ago
Rich Harris	3d8aad2f6c	fix skipped intros	8 years ago
Rich Harris	f9db67edbb	nested component transitions	8 years ago
Rich Harris	0e43507660	add skipIntroByDefault compiler option (#547)	8 years ago
Rich Harris	a344afaa86	update tests	8 years ago
Rich Harris	d695d7b75a	update tests	8 years ago
Rich Harris	a19aec1ea9	assign custom methods to custom element prototype - fixes #1369	8 years ago
Rich Harris	dd61ceba66	minor fixes, update various tests	8 years ago
Rich-Harris	6e41ebe91b	component spread	9 years ago
Jacob Wright	97f74dc8a6	Make actions execute with the component context	9 years ago
Jacob Wright	a5ed6cbe18	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.	9 years ago