You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In combination with HTTP.jl middleware is defined as a function returning a function, i.e. what is called a higher order function.
If I get it right, then Revise.jl does not support revising such usecases yet, i.e. when calling auth_middleware(router) and auth_middleware being like auth_middleware(handler) = function(request::HTTP.Request) ... end.
If something inside the return function of auth_middleware changes, then it does not seem to be revised (despite HTTP.listen! calls Base.invokelatest.
Is this description correct? Maybe I am confused because of different aspects. If it is correct is there already a workaround to revise the functions returned by higher order functions?
The text was updated successfully, but these errors were encountered:
If I understand correctly, this is an issue about "data". Any values returned by code are "data," even if those data are functions. You have to regenerate valid data if you revise in ways that would change the returned data. For example:
mycode() =1
result = [mycode()]
# Now edit mycode() to return 2
This does not update result: you have to recompute it manually.
In combination with HTTP.jl middleware is defined as a function returning a function, i.e. what is called a higher order function.
If I get it right, then Revise.jl does not support revising such usecases yet, i.e. when calling
auth_middleware(router)
andauth_middleware
being likeauth_middleware(handler) = function(request::HTTP.Request) ... end
.If something inside the return function of
auth_middleware
changes, then it does not seem to be revised (despiteHTTP.listen!
callsBase.invokelatest
.Is this description correct? Maybe I am confused because of different aspects. If it is correct is there already a workaround to revise the functions returned by higher order functions?
The text was updated successfully, but these errors were encountered: