ibsciss / ruby-middleware Goto Github PK

I find we're often trying to change the arguments provided to one of our middlewares... but it doesn't work if I replace it.

stack.replace SomeMiddleware,
                        SomeMiddleware,
                         configuration: "different_config"

The new configuration is not applied :-(.

• proper version in install
• change lambda syntaxe

This gem looks alright. How about releasing something?

Can we get a new release on rubygems to include the latest kwargs changes in main?

Sure would be nice!

Hi @lilobase! I'm looking to move to this fork for my project as mitchell's original hasn't been updated for a while

Just looking through #7 #5 #8 and I can see there's been some movement last year around updating docs, fixing a bug and adding tags to the git repo... but there's not been any changes to the repo since 2015 still

Can I help? I don't want to end up forking again if I can help it 😄

Hi guys.

Do we have some kind of motivation to set the value of env to nil?

Cause, to my mind, it makes some features of current Ruby usable only in certain ways.

For example - keyword arguments:

Middleware::Builder.new do |b|
  b.use -> (a: 1, b: 3) { p a, b }
end.call

So, in order for that snippet to work, I have to pass some value (empty hash) to the #call method.
That snippet would fail due to the fact, that default argument is nil.

The second aspect is about explicitness of what we're trying to achieve. With nil as default value protocol makes unexpected decision for me.

Thanks in advance, waiting for your comments. :)