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

BufferedChangeEventInit shouldn't be optional in BufferedChangeEvent constructor #350

Merged
merged 1 commit into from
Mar 19, 2024
Merged

BufferedChangeEventInit shouldn't be optional in BufferedChangeEvent constructor #350

merged 1 commit into from
Mar 19, 2024

Conversation

jyavenard
Copy link
Member

@jyavenard jyavenard commented Mar 18, 2024 •
edited by pr-preview bot
Loading

Fixes #349.

Preview | Diff

@jyavenard jyavenard requested review from padenot and wolenetz and removed request for padenot March 18, 2024 23:44
@jyavenard jyavenard merged commit 47948b4 into w3c:main Mar 19, 2024
2 checks passed
@jyavenard jyavenard deleted the pr_349 branch March 19, 2024 02:44
github-actions bot added a commit that referenced this pull request Mar 19, 2024
@jyavenard @github-actions
BufferedChangeEventInit shouldn't be optional in BufferedChangeEvent …
de65d31 
…constructor (#350)

SHA: 47948b4
Reason: push, by jyavenard

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@marcoscaceres marcoscaceres marcoscaceres approved these changes

@wolenetz wolenetz Awaiting requested review from wolenetz

@padenot padenot Awaiting requested review from padenot

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

BufferedChangeEventInit shouldn't be optional in BufferedChangeEvent constructor
2 participants
@jyavenard @marcoscaceres