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

Notification doesn't resolve URN target objects, which may mean missed notifications. #578

Open
idearat opened this issue Jan 25, 2022 · 0 comments
Assignees
Labels
LIMIT not quite a bug... but frustrating/limiting Signaling signal / notification issues

Comments

@idearat
Copy link
Contributor

idearat commented Jan 25, 2022

When you register a URN as the handler for a signal, the system doesn't resolve URNs to their target object(s). This is proper when the URN is a pure scalar/non-mutable value holder, but it will fail if you used a URN to a Type or other instance.

@idearat idearat added LIMIT not quite a bug... but frustrating/limiting Signaling signal / notification issues labels Jan 25, 2022
@idearat idearat self-assigned this Jan 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
LIMIT not quite a bug... but frustrating/limiting Signaling signal / notification issues
Projects
None yet
Development

No branches or pull requests

1 participant