-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
decompile fails when referencing ef core 5 #2232
Comments
OK, some additional research on this, ICSharpCode.Decompiler references Humanizer.Core >= 2.2.0 while efcore references Humanizer.Core >= 2.8.26 |
yes, there is a breaking change in Humanizer.Core: The decompiler expects: The breaking change is due to the added optional parameter. Note that both are from the same major version, seems like Humanizer does not follow semver rules... not sure how we could fix this. |
Not sure, if updating to a newer version of Humanizer is a good idea. @dgrunwald @christophwille what do you think? |
Once Humanizer fixes their issue, I wonder how long before ef core pulls in the new package.... sigh.. Thank you for your fast response. |
https://www.nuget.org/packages/Microsoft.CodeAnalysis.CSharp.Workspaces/ This locks in our dependency, right? |
yes, so I guess, Humanizer should fix their bug. |
fyi, we are considering to copy source the parts of Humanizer (and make internal) we need. That way we could drop the dependency of Humanizer altogether and make the scenarios where a newer version is needed easily possible. |
…Humanizer. Therefore we copy the relevant parts and remove the dependency in order to avoid such problems in the future.
…Humanizer. Therefore we copy the relevant parts and remove the dependency in order to avoid such problems in the future.
…Humanizer. Therefore we copy the relevant parts and remove the dependency in order to avoid such problems in the future.
Steps to reproduce
Error message shown
Details
The text was updated successfully, but these errors were encountered: