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

Throw exception when trying to use non-backed enum types #11176

Merged
merged 1 commit into from
Jan 23, 2024
Merged

Throw exception when trying to use non-backed enum types #11176

merged 1 commit into from
Jan 23, 2024

Conversation

thePanz
Copy link
Contributor

@thePanz thePanz commented Jan 19, 2024

This solves #11173

@greg0ire
Copy link
Member

It seems there are several CI jobs failing. Please take a look at this guide for more on how to handle those.

@thePanz
Copy link
Contributor Author

thePanz commented Jan 22, 2024

@greg0ire Pushed some more fixes.

I did not run phpunit still as I do not have all the required DB backends tho

@greg0ire
Copy link
Member

greg0ire commented Jan 22, 2024

You only need SQLite to run most tests, and you need nothing at all to run the tests you wrote.

@greg0ire greg0ire added this to the 2.17.4 milestone Jan 23, 2024
@greg0ire greg0ire merged commit fbc8e67 into doctrine:2.17.x Jan 23, 2024
58 checks passed
@thePanz thePanz deleted the fix-11173-get-name-on-null-non-backed-enum branch January 24, 2024 08:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants