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

subscriber: fix filter::ParseError accidentally being renamed #1558

Merged
merged 1 commit into from
Sep 13, 2021

Conversation

hawkw
Copy link
Member

@hawkw hawkw commented Sep 13, 2021

I accidentally renamed this type in PR #1550 after getting confused by a
renaming import that I thought was publicly re-exported, but it wasn't
actually..sorry about that!

This commit renames (or...un-renames?) the type. Whoopsie!

Fixes #1557

I accidentally renamed this type in PR #1550 after getting confused by a
renaming import that I thought was publicly re-exported, but it wasn't
actually..sorry about that!

This commit renames (or...un-renames?) the type. Whoopsie!
@hawkw hawkw requested a review from a team as a code owner September 13, 2021 17:33
@hawkw hawkw merged commit 6df3fd1 into v0.1.x Sep 13, 2021
@hawkw hawkw deleted the eliza/fix-accidental-rename branch September 13, 2021 17:44
hawkw added a commit that referenced this pull request Sep 13, 2021
# 0.2.22 (September 13, 2021)

This fixes a regression where the `filter::ParseError` type was
accidentally renamed.

### Fixed

- **filter**: Fix `filter::ParseError` accidentally being renamed to
  `filter::DirectiveParseError` ([#1558])

[#1558]: #1558
hawkw added a commit that referenced this pull request Sep 13, 2021
# 0.2.22 (September 13, 2021)

This fixes a regression where the `filter::ParseError` type was
accidentally renamed.

### Fixed

- **filter**: Fix `filter::ParseError` accidentally being renamed to
  `filter::DirectiveParseError` ([#1558])

[#1558]: #1558
davidbarsky pushed a commit that referenced this pull request Nov 29, 2021
I accidentally renamed this type in PR #1550 after getting confused by a
renaming import that I thought was publicly re-exported, but it wasn't
actually..sorry about that!

This commit renames (or...un-renames?) the type. Whoopsie!

Fixes #1557
hawkw added a commit that referenced this pull request Mar 23, 2022
I accidentally renamed this type in PR #1550 after getting confused by a
renaming import that I thought was publicly re-exported, but it wasn't
actually..sorry about that!

This commit renames (or...un-renames?) the type. Whoopsie!

Fixes #1557
hawkw added a commit that referenced this pull request Mar 23, 2022
I accidentally renamed this type in PR #1550 after getting confused by a
renaming import that I thought was publicly re-exported, but it wasn't
actually..sorry about that!

This commit renames (or...un-renames?) the type. Whoopsie!

Fixes #1557
hawkw added a commit that referenced this pull request Mar 24, 2022
I accidentally renamed this type in PR #1550 after getting confused by a
renaming import that I thought was publicly re-exported, but it wasn't
actually..sorry about that!

This commit renames (or...un-renames?) the type. Whoopsie!

Fixes #1557
hawkw added a commit that referenced this pull request Mar 24, 2022
I accidentally renamed this type in PR #1550 after getting confused by a
renaming import that I thought was publicly re-exported, but it wasn't
actually..sorry about that!

This commit renames (or...un-renames?) the type. Whoopsie!

Fixes #1557
hawkw added a commit that referenced this pull request Mar 24, 2022
I accidentally renamed this type in PR #1550 after getting confused by a
renaming import that I thought was publicly re-exported, but it wasn't
actually..sorry about that!

This commit renames (or...un-renames?) the type. Whoopsie!

Fixes #1557
hawkw added a commit that referenced this pull request Mar 24, 2022
I accidentally renamed this type in PR #1550 after getting confused by a
renaming import that I thought was publicly re-exported, but it wasn't
actually..sorry about that!

This commit renames (or...un-renames?) the type. Whoopsie!

Fixes #1557
hawkw added a commit that referenced this pull request Mar 24, 2022
I accidentally renamed this type in PR #1550 after getting confused by a
renaming import that I thought was publicly re-exported, but it wasn't
actually..sorry about that!

This commit renames (or...un-renames?) the type. Whoopsie!

Fixes #1557
hawkw added a commit that referenced this pull request Mar 24, 2022
I accidentally renamed this type in PR #1550 after getting confused by a
renaming import that I thought was publicly re-exported, but it wasn't
actually..sorry about that!

This commit renames (or...un-renames?) the type. Whoopsie!

Fixes #1557
hawkw added a commit that referenced this pull request Mar 24, 2022
I accidentally renamed this type in PR #1550 after getting confused by a
renaming import that I thought was publicly re-exported, but it wasn't
actually..sorry about that!

This commit renames (or...un-renames?) the type. Whoopsie!

Fixes #1557
hawkw added a commit that referenced this pull request Mar 24, 2022
I accidentally renamed this type in PR #1550 after getting confused by a
renaming import that I thought was publicly re-exported, but it wasn't
actually..sorry about that!

This commit renames (or...un-renames?) the type. Whoopsie!

Fixes #1557
kaffarell pushed a commit to kaffarell/tracing that referenced this pull request May 22, 2024
…o-rs#1558)

I accidentally renamed this type in PR tokio-rs#1550 after getting confused by a
renaming import that I thought was publicly re-exported, but it wasn't
actually..sorry about that!

This commit renames (or...un-renames?) the type. Whoopsie!

Fixes tokio-rs#1557
kaffarell pushed a commit to kaffarell/tracing that referenced this pull request May 22, 2024
# 0.2.22 (September 13, 2021)

This fixes a regression where the `filter::ParseError` type was
accidentally renamed.

### Fixed

- **filter**: Fix `filter::ParseError` accidentally being renamed to
  `filter::DirectiveParseError` ([tokio-rs#1558])

[tokio-rs#1558]: tokio-rs#1558
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