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

channels: make reply scry response match mark type #3227

Merged
merged 1 commit into from
Feb 9, 2024

Conversation

Fang-
Copy link
Member

@Fang- Fang- commented Feb 9, 2024

Scrying for a reply message would produce a noun marked with the %channel-reply mark, but the noun itself wouldn't nest in the type of that mark.

Here, we add a cast to the appropriate type, and "unversion" the reply noun that was being produced to coerce it into the correct shape.

Resolves LAND-1531.

Scrying for a reply message would produce a noun marked with the
%channel-reply mark, but the noun itself wouldn't nest in the type of
that mark.

Here, we add a cast to the appropriate type, and "unversion" the reply
noun that was being produced to coerce it into the correct shape.

Resolves LAND-1531.
@Fang- Fang- added the bug label Feb 9, 2024
@Fang- Fang- requested a review from arthyn February 9, 2024 11:45
Copy link

linear bot commented Feb 9, 2024

Copy link
Member

@arthyn arthyn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, should this be going out sooner than later? if so we should target staging

@Fang-
Copy link
Member Author

Fang- commented Feb 9, 2024

We don't depend on this scry endpoint ourselves (at least, I can't find scries for this endpoint in our codebase, and nothing has appeared to be broken by this), so no particular rush on this.

It does make for a confusing outward-facing api, where correct usage breaks it, but we've received no reports of this being bugged from anyone. Technically, this PR constitutes a breaking scry api change, albeit a small one.

@arthyn arthyn merged commit ddafc50 into develop Feb 9, 2024
1 check passed
@arthyn arthyn deleted the m/unversion-reply-scry branch February 9, 2024 23:25
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.

2 participants