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

Ensure that source list message doesn't try to send proxy #251

Merged
merged 1 commit into from
May 30, 2023

Conversation

Carifio24
Copy link
Member

This PR solves the same problem as #218, just in a slightly different place. That PR ensured that the last selected source couldn't be sent as a proxy, but we can actually get the same issue when sending the message describing the list of currently selected sources. This is a problem for downstream applications where the app's statusMessageDestination is non-null (e.g. pywwt), since the postMessage call app-side will fail as the proxy can't be cloned.

This PR refactors the isProxy/toRaw logic into the prepareForMessaging method, which gets called during the dispatch for both message types (and fits logically, as this is necessary to prepare the data for messaging).

@pkgw pkgw merged commit 900a45a into WorldWideTelescope:master May 30, 2023
9 checks passed
pkgw added a commit to pkgw/pywwt that referenced this pull request May 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants