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.

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

DomView#subviews() List should update after #artifact() #157

Open
issa-tseng opened this issue Jul 24, 2019 · 2 comments
Open

DomView#subviews() List should update after #artifact() #157

issa-tseng opened this issue Jul 24, 2019 · 2 comments
Labels

Comments

@issa-tseng
Copy link
Owner

right now if you do domview.subviews() before you call artifact() you get an empty List back.

but then if you call .artifact() later, that list does not update with the new subviews.

@issa-tseng issa-tseng added the bug label Jul 24, 2019
@issa-tseng
Copy link
Owner Author

one possible solution is to refactor binding generation to be based on a Managed Varying.

this change would also allow wireEvents to not force artifact, but instead autowire once the artifact actually does exist.

@issa-tseng
Copy link
Owner Author

(same problem with stdlib listview right now)

@issa-tseng issa-tseng changed the title DomView.subviews() List should update after #artifact() DomView#subviews() List should update after #artifact() Aug 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant