options for controlling auto-start of effects #17
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
feat: add a
static autoStartEffectsoption for classes that use the@effectdecorator, that when set tofalsewill not auto-start effects on class instantiation. This is useful withstartEffects()for starting effects later.feat: add a new
addEffectFnmethod toEffectfulmixing andEffectsclass for adding an effect function without starting it, as an alternative to thecreateEffectmethod, useful for starting added effects later with thestartEffectsmethod.re-export private APIs from
_state.tsfrom the index so that downstream consumers like@lume/elementdon't have to update importmaps and break consumers