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

Review Observe handler in the algorithms #455

Open
relu91 opened this issue Feb 20, 2023 · 2 comments
Open

Review Observe handler in the algorithms #455

relu91 opened this issue Feb 20, 2023 · 2 comments
Labels
bug Error, flaw or fault in the specification that causes misunderstandings and/or incorrect/unexpected for next iteration Planned or postponed topics for the future

Comments

@relu91
Copy link
Member

relu91 commented Feb 20, 2023 •
edited

Note: the observe handler is not mentioned later on in the algorithm. Also, I think the observe handler now has another function: it is called when somebody observes the property.

Originally posted by @relu91 in #450 (comment)
@relu91
Copy link
Member Author

relu91 commented Dec 11, 2023 •
edited

I think the problem still remains. The introduction text still mentions some interaction with the ObserveHandler when emitting property changes. I'm labelling as a bug.

@relu91 relu91 added the bug Error, flaw or fault in the specification that causes misunderstandings and/or incorrect/unexpected label Dec 11, 2023
@zolkis
Copy link
Contributor

zolkis commented Dec 11, 2023 •
edited

We have internal slot for observe handles. We can include a reference with the prose.

@relu91 relu91 added the for next iteration Planned or postponed topics for the future label Jan 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Error, flaw or fault in the specification that causes misunderstandings and/or incorrect/unexpected for next iteration Planned or postponed topics for the future
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zolkis @relu91