Skip to content

Fixed various typos #5716

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

Merged
merged 4 commits into from
Oct 4, 2022
Merged

Fixed various typos #5716

merged 4 commits into from
Oct 4, 2022

Conversation

nexxai
Copy link
Contributor

@nexxai nexxai commented Oct 3, 2022

Q A
Type improvement
Fixed issues n/a

Summary

Cleaning up typos throughout the codebase

@nexxai
Copy link
Contributor Author

nexxai commented Oct 3, 2022

@greg0ire Not sure if you get notified on new pushes, so just added the backwards-compatible function

@greg0ire
Copy link
Member

greg0ire commented Oct 3, 2022

I do get notified.

@greg0ire
Copy link
Member

greg0ire commented Oct 3, 2022

You can run git rebase 2bb77fe --exec vendor/bin/phpcbf to fix the coding standard issues on the right commit.

@nexxai
Copy link
Contributor Author

nexxai commented Oct 3, 2022

Thanks for all your help!

@greg0ire
Copy link
Member

greg0ire commented Oct 3, 2022

I've done it for you, and also, I fixed up the backwards-compat layer commit into the right commit. 👍

@nexxai
Copy link
Contributor Author

nexxai commented Oct 3, 2022

Oh wow, thank you so much!

@@ -186,11 +186,19 @@ public function spansColumns(array $columnNames)
}

/**
* Checks if the other index already fulfills all the indexing and constraint needs of the current one.
* Keeping misspelled function name for backwards compatibility
Copy link
Member

Choose a reason for hiding this comment

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

Although we need to keep the method around in the current major release, it should be deprecated and removed in the next major.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yep, @greg0ire already mentioned that.

Copy link
Member

Choose a reason for hiding this comment

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

@morozov I think this can be merged as is, then the deprecation can be added on 3.5.x

Copy link
Member

Choose a reason for hiding this comment

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

@nexxai please don't mark as resolved conversations you do not open in general, and here in particular because it hides my comment.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Oh no, I'm sorry! I'll leave them open for the commenter to close. Again, my apologies.

Copy link
Member

Choose a reason for hiding this comment

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

No worries.

@greg0ire greg0ire requested a review from morozov October 4, 2022 18:36
Copy link
Member

@morozov morozov left a comment

Choose a reason for hiding this comment

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

#5716 (comment) doesn't seem to be addressed. The method needs to be annotated as deprecated, and a note in UPGRADE.md added.

@greg0ire
Copy link
Member

greg0ire commented Oct 4, 2022

@morozov have you seen my comment on this?

@morozov
Copy link
Member

morozov commented Oct 4, 2022

No, I missed that one.

@greg0ire greg0ire added this to the 3.4.6 milestone Oct 4, 2022
@greg0ire greg0ire merged commit 27a6f55 into doctrine:3.4.x Oct 4, 2022
@greg0ire
Copy link
Member

greg0ire commented Oct 4, 2022

No worries :)

@nexxai thanks for this contribution! Once #5720 is merged, please send a PR to introduce the deprecation and upgrade note requested above, targeting 3.5.x this time.

@nexxai
Copy link
Contributor Author

nexxai commented Oct 4, 2022

Confirmed: I've subscribed to #5720 and will send the appropriate PR to 3.5.x when it's been merged.

Thanks for both of your help and understanding through this process.

@derrabus derrabus changed the title Typofixes Fixed various typos Oct 18, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 19, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants