Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Decouple decorators from reactivity infra of engine #70

Closed
davidturissini opened this issue Feb 6, 2018 · 3 comments
Closed

Decouple decorators from reactivity infra of engine #70

davidturissini opened this issue Feb 6, 2018 · 3 comments
Assignees
@caridy

Comments

@davidturissini
Copy link
Contributor

Description

Today, decorators are tightly coupled to engine reactivity. We should de-couple these so decorators can be moved into their own repo and have limited knowledge of engine internals.
@diervo diervo removed the gus-story label Feb 16, 2019
@caridy
Copy link
Contributor

caridy commented May 15, 2019 •
edited
Loading

part of #1038, but there is more to do here. at first glance, if each engine version contains its own mechanism to observe objects passed into instances controlled by that engine version, it should be fine to have them coupled.

@caridy
Copy link
Contributor

caridy commented Aug 12, 2019

This will partially solved by #1417

@jmsjtu
Copy link
Member

jmsjtu commented Dec 19, 2023

We plan to use signals for reactivity and native decorators in the future, closing this issue.

@jmsjtu jmsjtu closed this as completed Dec 19, 2023
pmdartus pushed a commit that referenced this issue Nov 12, 2024
@ravijayaramappa
fix: scoped slots - add table of content (#70)
0316e1e
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@caridy caridy

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@caridy @davidturissini @diervo @jmsjtu