-
Notifications
You must be signed in to change notification settings - Fork 250
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
a small working example #65
Conversation
Thanks, Patrick. Why do you prefer this example to the previous one? |
Yes, I was just starting on learning about Rack in general. From my understanding, there are 3 types of rack app's used:
When learning on Rack, the lambda function seems to be the standard use case, which I was thinking that showing this in an example might be nice. |
As a reference, there is another PR to add |
@scepticulous I would prefer the improved example as well. I agree with you. If some people like other use cases (types)' examples in the future, I want to split the example section from README, and link from the README to |
@scepticulous thanks for the ping - unfortunately, I am not working with Ruby anymore for some years. |
This PR implements PRs #65, #74 and #78. Some of the PRs contain similar content and other are no longer based on the current readme. THis is an attempt to clean up the readme state. In addition some suggestions for further updates are part of the PR to raise the discussion about: List of maintainers and the format (email or github username) and the copyright text we want to have (or not have).
Implemented in #174 |
Hi,
just as an idea to use a working example in the README
It's maybe easier to see that such things as headers, etc. can be tested.
Well... this commit is not rocket science, but maybe would be interesting for some or the other. Actually in combination with Capybara this might open up new ways for testing.
Patrick