-
Notifications
You must be signed in to change notification settings - Fork 2
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
Not follow standard filename convention #5
Comments
Historical reasons, I guess. Rack is a pretty old library and this naming convention wasn't as strict back then (I am not even sure whether it wasn't just considered a "Rails convention"). Changing the file name of |
I noticed that Rack takes capitalized hash key like Are these historical, too? They are queer to me. |
I think the case here is a bit different: https://github.com/codereading/rack/blob/rack-1.4/lib/rack/server.rb#L142-173 As you can see, most options are downcased, except the options that are directly passed to the Handler. I think its a kind of "namespacing". |
I see. Thanks @skade ! |
Why that could be happen? I see it load by using |
One reason might be that [1] http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/41149 |
Following Ruby standard filename convention, filename should be all in lowercase and separate each word by underscore, but I see some filenames break this rule:
I feel it should be
Do have any ideas why they have filenames like this?
The text was updated successfully, but these errors were encountered: