Giter Site home page Giter Site logo

Comments (4)

gerardtoconnor avatar gerardtoconnor commented on May 6, 2024 1

Both this continuation update and task were done for performance reasons, you can read blog post I did to explain performance benefits here if your interested.

https://medium.com/@gerardtoconnor/carry-on-continuation-over-binding-pipelines-for-functional-web-58bd7e6ea009

It's a slightly more complex way of doing the handlers but there is a focus on performance and the consensus was it was worth breaking now for the long run.

If you have anymore issues let me know, happy to help.

from giraffe.

dustinmoris avatar dustinmoris commented on May 6, 2024 1

Apologies for this issue. Even though I have updated the latest giraffe-template, the previous versions break now when you pull the beta package from an alpha template. I should have not referenced giraffe with a wildcard in the .fsproj. I will set it to a specific version going forward with the new template releases, but meanwhile if someone runs into this issue you can either pin the latest giraffe alpha package, or preferably update the error handler to match the new beta. You can simplify the error handler even further:

let errorHandler (ex : Exception) (logger : ILogger) =
    logger.LogError(EventId(), ex, "An unhandled exception has occurred while executing the request.")
    clearResponse >=> setStatusCode 500 >=> text ex.Message

Also please update the giraffe-template by running:

dotnet new -i giraffe-template::0.1.7

from giraffe.

gerardtoconnor avatar gerardtoconnor commented on May 6, 2024

The error handler needs to be updated to use new HttpHandler format such that it additionally accepts a 'HttpFunc' functions as well as 'HttpContext' like 'fun next ctx ->. ..'

In the last line where handlers are composed, instead of 'ctx |> (handler)' you need to apply both parameters to functions like '(handler) next ctx'

from giraffe.

ryukinix avatar ryukinix commented on May 6, 2024

Yes, I understand. Your tip fixed the problem. I can know why this change was made? Is related to the new Task support #53?

If anyone struggle with it too, the new errorHandler which works is it:

// ---------------------------------
// Error handler
// ---------------------------------

let errorHandler (ex : Exception) (logger : ILogger) (next: HttpFunc) (ctx : HttpContext) =
    logger.LogError(EventId(0), ex, "An unhandled exception has occurred while executing the request.")
    (clearResponse >=> setStatusCode 500 >=> text ex.Message) next ctx

from giraffe.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.