-
Notifications
You must be signed in to change notification settings - Fork 85
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
Giraffe.ViewEngine.StrongName breaks compatability with Giraffe server #452
Comments
thanks!
this will only work in an environment that does not care about this strong naming clusterfck. I really regret supporting this, and I think i might actually revert it in a future version. But for the moment i have no idea what i could do about this that would not lead to either a) breaking compatibility for netfx/strong naming stuff or b) depend on the Giraffe team on signing the original package. |
However, a workaround could be including the raw html output, which would be |
Description
Hey, thanks for you effort in this library, it really is amazing.
I came about an issue with the fork project mentioned here giraffe-fsharp/Giraffe.ViewEngine#23
It is currently not possible to render a chart to json in a giraffe backend via toJson gChart as it was added in version 4.1.0 which doesn't work with giraffe due to a presence of forked
Giraffe.ViewEngine.StrongName
packageRepro steps
Expected behavior
Project builds
Actual behavior
Known workarounds
Fork Plotly.Net and revert the change
Related information
The text was updated successfully, but these errors were encountered: