Skip to content

Conversation

@chrisrink10
Copy link
Member

Fixes #1118

@chrisrink10 chrisrink10 marked this pull request as ready for review November 11, 2024 16:48
@chrisrink10 chrisrink10 marked this pull request as draft November 11, 2024 18:13
@chrisrink10 chrisrink10 marked this pull request as ready for review November 11, 2024 19:16
@chrisrink10 chrisrink10 marked this pull request as draft November 11, 2024 19:45
@chrisrink10 chrisrink10 force-pushed the fix/reader-dont-consume-tagged-literal-in-conditional branch 2 times, most recently from 9d4dc34 to 3ce8cbd Compare November 12, 2024 14:41
@chrisrink10 chrisrink10 force-pushed the fix/reader-dont-consume-tagged-literal-in-conditional branch from 3ce8cbd to a2afcbc Compare November 12, 2024 15:17
@chrisrink10 chrisrink10 marked this pull request as ready for review November 12, 2024 15:23
@chrisrink10 chrisrink10 merged commit fb28054 into main Nov 12, 2024
12 checks passed
@chrisrink10 chrisrink10 deleted the fix/reader-dont-consume-tagged-literal-in-conditional branch November 12, 2024 15:35
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.

Unknown data readers in non-selected reader conditional paths can prevent reading

1 participant